Austin/api extensions upgrade #1429
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Note: another PR will be needed in the cluster-turndown repo that accomplishes the same thing |
AjayTripathy
approved these changes
May 23, 2022
|
@wolfeaustin we will want to merge this into the v1.93 branch as well, since I do think it makes sense to patch this in. |
This was referenced May 27, 2022
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What does this PR change?
Upgrade to apiextensions.k8s.io/v1 to successfully install cluster controller for automated turndown
Does this PR rely on any other PRs?
How does this PR impact users? (This is the kind of thing that goes in release notes!)
Users will be able to successfully install cluster controller for automated turndown on K8s versions < v1.22
Links to Issues or ZD tickets this PR addresses or fixes
How was this PR tested?
helm upgrade with PR tweaks. Schedule automated turndown
Have you made an update to documentation?
No