update CRD version to v1 #126
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
jensfr
added
the
do-not-merge/hold
pmores
approved these changes
Jul 15, 2021
v1beta1 is not supported anymore in kubernetes. We need to switch to version v1. To be clear, this is about the version of the CustomResourceDefinition kind, not about the version of kataconfig. Signed-off-by: Jens Freimann <jfreimann@redhat.com>
jensfr
force-pushed
the
update-crd-version
branch
from
164658c
to
4e94296
Compare
jensfr
removed
the
do-not-merge/hold
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.
Use apiextensions.k8s.io/v1 instead of v1beta1, which is not supported anymore. We need to switch to
version v1 or we can't create our own KataConfig CRD anymore. To be clear,
we're updating the version of the CustomResourceDefinition kind, not the version of kataconfig.
See kubernetes/kubernetes#79604