chore(manifests): switch to full CRDs by default #15003
Draft
Conversation
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
Signed-off-by: Mason Malone <[email protected]>
MasonM
force-pushed
the
swtich-to-full-CRDs
branch
from
abfd0ed to
ed8ff6c
Compare
Member
Author
|
/retest |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Motivation
After the work in #14044, the full CRDs are now usable, and no issues have been reported. This switches the install manifests to use them by default.
Modifications
Update the the
kustomization.yamlfiles to reference the full CRDsVerification
Ran
make manifests-validate(which is also run in CI builds)Documentation
Remove the now-outdated "Full CRDs" section from the installation docs