DOCS-3007: Tweak the breaking change note for Calico Cloud v23 - #2922
Open
ctauchen wants to merge 1 commit into
Open
DOCS-3007: Tweak the breaking change note for Calico Cloud v23#2922ctauchen wants to merge 1 commit into
ctauchen wants to merge 1 commit into
Conversation
✅ Deploy Preview succeeded!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for calico-docs-preview-next ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Contributor
There was a problem hiding this comment.
Pull request overview
Updates Calico Cloud v23.0.0 (versioned docs) release notes to explicitly call out the allow-tigera → calico-system tier rename as a potential breaking change and provide upgrade guidance for user-created resources.
Changes:
- Add an “Updating” note describing what can break and what to verify/remove before upgrading (policies, tier ordering, RBAC, queries).
- Adjust a stray formatting artifact later in the release notes content.
Suppressed comments (2)
calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx:79
- This list item is currently a comma splice and reads awkwardly; splitting into two sentences improves clarity.
* Tiers that you ordered relative to `allow-tigera`, the new `calico-system` tier is the same order as `allow-tigera`.
calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx:83
- The recommendation sentence is a comma splice; splitting into two sentences (and adding a comma after “needed”) improves readability.
**Recommendation:** Do not add policies to the $[prodname] tier, if changes are needed create a separate tier and add your policies there.
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
Comment on lines
+74
to
+78
| * ***Potential breaking change:*** If you have dependencies on the `allow-tigera` tier those dependencies will need to be updated. | ||
| $[prodname] moves its own policies into the new `calico-system` tier during the upgrade, but it does not update resources that you created. | ||
| Before you upgrade, review anything that refers to the tier by name, including: | ||
| * Network policies that you added to the `allow-tigera` tier, these must be removed before starting the upgrade. | ||
| * If you do not remove your network policies from the `allow-tigera` tier, the install will block until they are removed. |
Erik Stidham's wording from ctauchen#16, rebased onto main. The note now calls the tier rename a potential breaking change, since it only breaks clusters that depend on allow-tigera. It also says what a user has to do rather than only what to review: network policies in allow-tigera must be removed before the upgrade starts, or the install blocks until they are, and calico-system keeps the same order as allow-tigera. It closes with the recommendation to keep user policies out of the Calico Cloud tier. The original commit was written against the DOCS-3007 branch, where the policy-tiers page is already renamed to calico-system. On main that page is still allow-tigera, so the link points there. It moves with the rename when #2918 merges. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ctauchen
force-pushed
the
DOCS-3007-tier-note
branch
from
August 14, 2026 21:54
73b9539 to
f3cb126
Compare
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.
Calico Cloud 23.0.0 renamed the allow-tigera tier to calico-system, and the 23.0.0 release notes never flagged it. This adds Erik Stidham's version of that note, taken from ctauchen#16 and rebased onto main. The commit keeps his authorship.
What the note says that the earlier draft did not:
One deviation from Erik's commit. He wrote it against the DOCS-3007 branch, where the policy-tiers page is already renamed, so his link points at calico-system.mdx. That page does not exist on main yet and onBrokenLinks is set to throw, so the link here points at the current allow-tigera.mdx. It moves with the rename when #2918 merges.
#2918 also adds a version of this note. Its release-notes change should be dropped once this merges, or the two will conflict.
Reviewers, once the deploy preview builds, the note is in the version 23.0.0 section under Updating: /calico-cloud/release-notes
DOCS-3007: https://tigera.atlassian.net/browse/DOCS-3007
CI-2032: https://tigera.atlassian.net/browse/CI-2032