Repository navigation
DOCS-3057: Remove tech preview notices from features that are GA - #3051
Merged
Merged
Conversation
Native v3 CRDs and selector-scoped Felix configuration both reached general availability in Calico Open Source 3.33. The 3.33 release notes say so and data/feature-status.yaml records it, but four notices still described them as tech preview, so the release notes and the feature pages contradicted each other in published docs. Removes the tech preview notices from the two native v3 CRD tabs in the on-premises install page, in both the unversioned tree and the 3.33 snapshot, and from the selector-scoped Felix configuration section and the Felix configuration precedence list. The 3.33 snapshot was already correct for the two Felix pages while the unversioned tree was not, so those files now match the snapshot.
✅ Deploy Preview succeeded!Built without sensitive environment variables
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Copilot review overview
🟢 Approval recommended
The changes consistently align the affected documentation with the 3.33 release notes and feature-status metadata.
Review effort: Balanced
Findings: None
What changed in this PR
Removes stale technology-preview notices from features that became generally available in Calico OSS 3.33.
Changes:
- Removes native v3 CRD preview notices from current and 3.33 installation docs.
- Removes selector-scoped Felix configuration preview labeling.
| File | Description |
|---|---|
calico/reference/resources/felixconfig.mdx |
Removes outdated Felix preview notice. |
calico/reference/felix/configuration.mdx |
Removes preview labeling from precedence list. |
calico/getting-started/kubernetes/self-managed-onprem/onpremises.mdx |
Removes outdated v3 CRD notices. |
calico_versioned_docs/version-3.33/getting-started/kubernetes/self-managed-onprem/onpremises.mdx |
Corrects the 3.33 snapshot notices. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
✅ Deploy Preview for calico-docs-preview-next ready!
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.
Native v3 CRDs and selector-scoped Felix configuration both reached general availability in Calico Open Source 3.33. The 3.33 release notes say so under Technology preview changes in this release, and data/feature-status.yaml records both as ga at 3.33. Four notices still described them as tech preview, so the release notes and the feature pages contradicted each other in published docs.
This removes those four notices:
The 3.33 snapshot was already correct for the two Felix pages while the unversioned tree was not, so those files now match the snapshot exactly.
Changed pages on the deploy previews. Note that the next pages are on the second preview host, because static/_redirects sends /calico/next/* away from the main preview.
This is the first change under DOCS-3057. The rest of that ticket replaces hand-written lifecycle notices with a shared component, and this reconciliation comes first so the migration does not carry stale statuses into structured metadata.
Related: DOCS-2999.