Open
Conversation
Lasserich
had a problem deploying
to
pr-e2e-approval
GitHub Actions
Failure
Lasserich
had a problem deploying
to
pr-e2e-approval
GitHub Actions
Failure
Lasserich
had a problem deploying
to
pr-e2e-approval
GitHub Actions
Failure
Lasserich
had a problem deploying
to
pr-e2e-approval
GitHub Actions
Failure
Contributor
Author
|
Elaborate on the right side more, what happens with different version APIs between provider versions? |
Contributor
|
I would recommend checking this document https://kubernetes.io/docs/tasks/extend-kubernetes/custom-resources/custom-resource-definition-versioning/ |
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
The following lines out best practices and decision criteria to take when migrating a resource version from version A to B.
Considering aspects like type and size of change of the CRD and managed resource.