Document v3 CRD mode as the default for new installs#2805
Open
caseydavenport wants to merge 9 commits into
Open
Document v3 CRD mode as the default for new installs#2805caseydavenport wants to merge 9 commits into
caseydavenport wants to merge 9 commits into
Conversation
…ent v3 manifest path
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
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
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.
Makes v3 CRD mode the documented default for new Calico installs, matching the operator change in tigera/operator#4973. New installs now get
projectcalico.org/v3served directly by CRDs with no aggregation API server. The v1 / aggregation-API-server path stays documented as an opt-out. Existing and upgraded clusters are unaffected - the operator picks the mode from the CRDs present and never flips an existing cluster.What's here:
v3_projectcalico_org.yaml). The operator and manifest installs that stay on the aggregation API server got a v3 opt-out note instead.Note on Enterprise: this assumes
v3_projectcalico_org.yamlships at the published EE manifests location. The release tooling already builds and publishes it (hashreleases and tagged releases both include it), so it should line up with real releases. The one gap is theee/master/dev location, which is stale and hasn't picked up the granular bundles - flagged to the DE team separately.