Change URN for apiregistration resources #1021
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
pgavlin
reviewed
Mar 5, 2020
Previously, the URN for apiregistration resources was of the form `apiregistration/Version:Kind`. This has been updated to the canonical form `apiregistration.k8s.io/Version:Kind`. Aliases have been added for the old URNs, so this change should not cause any resources to be updated.
lblackstone
force-pushed
the
lblackstone/apiregistration
branch
from
8763eb1 to
b4238d0
Compare
Merged
pgavlin
approved these changes
Mar 21, 2020
lukehoban
approved these changes
Mar 21, 2020
Open
1 task
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.
Proposed changes
Previously, the URN for apiregistration resources was of the form
apiregistration/Version:Kind. This has been updated to thecanonical form
apiregistration.k8s.io/Version:Kind. Aliases havebeen added for the old URNs, so this change should not cause
any resources to be updated.
Related issues (optional)