Apply operator-crds.yaml before creating custom resources #1834
+36
−18
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
Add command to create/apply operator-crds.yaml before custom-resources.yaml (installation, etc) to ensure CRDs are present. With the recent changes to the operator to manage CRDs, they are no longer included in the tigera-operator.yaml manifest, so there might be timing issues where the installation and other custom resources are attempted to be created before their definitions are present in the cluster.
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify site configuration. |
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify site configuration. |
|
Thanks, @coutinhop. I'm having trouble finding background information on this one. Can you send me details, tickets, etc? |
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.
Add command to create/apply operator-crds.yaml before custom-resources.yaml (installation, etc) to ensure CRDs are present.
With the recent changes to the operator to manage CRDs, they are no longer included in the tigera-operator.yaml manifest, so there might be timing issues where the installation and other custom resources are attempted to be created before their definitions are present in the cluster.
Product Version(s):
Issue:
Link to docs preview:
SME review:
DOCS review:
Additional information:
Merge checklist: