DOCS-3008: Add Calico Cloud 23.0.1 and delist 23.0.0 - #2919
Conversation
Calico Cloud 23.0.1 fixes CI-2032, an upgrade failure that three customers have hit. Upgrading to 23.0.0 moves the cluster DNS policy into the new calico-system tier while the allow-tigera tier remains at the same order with defaultAction Deny, so DNS to kube-dns hits the implicit deny in allow-tigera. Guardian cannot resolve the Calico Cloud address, it crash loops, and the upgrade never finishes. Engineering is removing 23.0.0 as an available version to install, so the docs need to match: - Replace the 23.0.0 image list with 23.0.1 on the private registry page, so air-gapped users mirror the fixed release. - Add a known issue to the 23.0.0 release notes that describes the DNS denial, states that 23.0.0 is no longer available to install, and points to 23.0.1. - Add a 23.0.1 release note with the single bug fix. - Point cloudUserVersion at v23.0.1 so the install and system requirements pages name the installable version. The image list and the release date are placeholders until the staging build is confirmed. The allow-tigera to calico-system rename and the missed breaking change note are DOCS-3007. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
✅ 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. |
There was a problem hiding this comment.
Pull request overview
Updates the Calico Cloud 23.2 versioned documentation to reflect that v23.0.1 is the installable release and v23.0.0 is delisted due to an upgrade/DNS regression, including updated release notes and the private-registry image list source.
Changes:
- Add 23.0.1 release notes and add a Known issue under 23.0.0 describing the DNS-deny upgrade failure and delisting.
- Update
cloudUserVersionfor Calico Cloud 23.2 docs to v23.0.1 so install/system-requirements pages display the correct installable version. - Replace the “latest” private-registry image-list selector entry from v23.0.0 to v23.0.1 (currently noted as a placeholder list).
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
| src/new/data/ccImageLists.js | Switch “latest” image-list entry to v23.0.1 (currently placeholder content flagged with TODO). |
| calico-cloud_versioned_docs/version-23-2/variables.js | Bump cloudUserVersion to v23.0.1 for the 23.2 versioned docs set. |
| calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx | Add 23.0.1 entry and a 23.0.0 Known issue detailing the upgrade/DNS regression and delisting guidance. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
| * Fixed a problem that denied cluster DNS traffic during an upgrade to version 23. | ||
| The Tigera Operator now adds the cluster DNS policy to the `calico-system` tier before it removes the policy from the `allow-tigera` tier, so $[prodname] components can resolve names for the whole upgrade. |
| // TODO(DOCS-3008): placeholder copied from the v23.0.0 list. Replace it with | ||
| // the v23.0.1 list once the release is in staging: | ||
| // curl -0 https://installer.calicocloud.io/manifests/<v23.0.1 manifest>/image-list | ||
| 'v23.0.1 (latest)': `quay.io/calico/istio-pilot:v3.32.1 |
There was a problem hiding this comment.
Left as is. The list itself still needs the real v23.0.1 output before merge.
The link check in make netlify fails on every pull request, which blocks the deploy preview for the main site. Two links are dead: - calicousers.slack.com returns 403 to the crawler on calico/reference/involved. Every other page links the same host with a trailing slash, and that form is already in the crawler skip list, so this makes the two involved pages consistent instead of adding a skip entry. - Cockroach Labs moved their docs to docs.cockroachlabs.com and dropped the stable alias, so the multi-cluster page linked from use-cases/cluster-mesh returns 404. The page still exists under a pinned version path. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.
Suppressed comments (3)
src/new/data/ccImageLists.js:5
- The v23.0.1 image list is explicitly marked as a placeholder copied from v23.0.0 and still contains a non-actionable manifest URL placeholder (
<v23.0.1 manifest>). This will produce incorrect guidance for air-gapped mirroring until it is replaced with the real v23.0.1 image-list output.
// TODO(DOCS-3008): placeholder copied from the v23.0.0 list. Replace it with
// the v23.0.1 list once the release is in staging:
// curl -0 https://installer.calicocloud.io/manifests/<v23.0.1 manifest>/image-list
'v23.0.1 (latest)': `quay.io/calico/istio-pilot:v3.32.1
calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx:18
- The sentence ends with "version 23." which reads as incomplete; it likely should name the specific affected version (23.0.0) or otherwise remove the trailing period fragment.
* Fixed a problem that denied cluster DNS traffic during an upgrade to version 23.
calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx:79
- Component name capitalization is inconsistent within this file (elsewhere it uses "Guardian"); this line should also capitalize the component name for clarity.
The guardian pod cannot resolve the address of $[prodname], so it enters `CrashLoopBackOff` and the upgrade does not finish.
- Name the affected upgrade path in the bug fix, so the note does not imply that every 23.x upgrade denies cluster DNS. Only upgrades from version 22 to 23.0.0 hit the problem. - Capitalize Guardian, which is how the architecture page names the component. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
- Drop the paragraph that introduced the 23.0.1 section. The bug fix and the known issue already say that 23.0.1 replaces 23.0.0. - Write the bug fix as a full report: name the release that introduced the problem, then state what works again. - Drop the admonition around the known issue and keep plain prose, so it reads as a known issue rather than a banner. - Shorten the known issue to the problem, the cause, and the workaround. The pod-level detail belongs in CI-2032, not here. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.
Suppressed comments (2)
src/new/data/ccImageLists.js:6
- This file is still using a placeholder image list copied from v23.0.0 (per the TODO). The PR description explicitly says not to merge until the v23.0.1 manifest image-list output replaces this placeholder (including the manifest version in the curl comment).
// TODO(DOCS-3008): placeholder copied from the v23.0.0 list. Replace it with
// the v23.0.1 list once the release is in staging:
// curl -0 https://installer.calicocloud.io/manifests/<v23.0.1 manifest>/image-list
'v23.0.1 (latest)': `quay.io/calico/istio-pilot:v3.32.1
quay.io/calico/istio-install-cni:v3.32.1
src/new/data/ccImageLists.js:4
- The placeholder curl command uses angle brackets (
<...>), which will be interpreted by many shells as input redirection if someone copy/pastes it. Use a non-shell-special placeholder token instead.
// TODO(DOCS-3008): placeholder copied from the v23.0.0 list. Replace it with
// the v23.0.1 list once the release is in staging:
// curl -0 https://installer.calicocloud.io/manifests/<v23.0.1 manifest>/image-list
| Version 23.0.1 replaces version 23.0.0, which is no longer available to install. | ||
| If a cluster runs version 23.0.0, upgrade it to version 23.0.1. |
|
|
||
| ### Known issues | ||
|
|
||
| :::warning[version 23.0.0 is no longer available to install] |
There was a problem hiding this comment.
no admonition. Just a known issue that describes the problem, the cause, the workaround (upgrade to 23.0.1).
There was a problem hiding this comment.
the short version, more abstract.
There was a problem hiding this comment.
Done in d529e19. The admonition is gone. The known issue is now plain prose: the problem, the cause, then the workaround.
There was a problem hiding this comment.
Done in d529e19. Cut to two sentences. The kube-dns hop, the Deny default action, the CrashLoopBackOff, and the calico-node by domain name variant are all in CI-2032 for anyone who needs them.
|
|
||
| Version 23.0.0 is no longer available to install. | ||
| Upgrade to [version 23.0.1](#23.0.1) instead, which fixes the problem. | ||
| If a cluster already runs version 23.0.0, upgrade it to version 23.0.1. |
There was a problem hiding this comment.
drop this paragraph.
There was a problem hiding this comment.
Done in d529e19. Dropped. The delisting and the pointer to 23.0.1 survive as two lines, since that is the workaround.
|
|
||
| ### Bug fixes | ||
|
|
||
| * Fixed a problem that denied cluster DNS traffic during an upgrade to version 23. |
There was a problem hiding this comment.
'problem introduced in 23.0.0'
finish bug report mentioning normal operation, problems resolved, etc.
There was a problem hiding this comment.
Done in d529e19. The bullet now reads "Fixed a problem introduced in version 23.0.0 that denied cluster DNS traffic when a cluster upgraded from version 22", then the operator ordering, then what works again: components keep resolving names, Guardian connects without crash looping, and the upgrade finishes.
| // TODO(DOCS-3008): placeholder copied from the v23.0.0 list. Replace it with | ||
| // the v23.0.1 list once the release is in staging: | ||
| // curl -0 https://installer.calicocloud.io/manifests/<v23.0.1 manifest>/image-list | ||
| 'v23.0.1 (latest)': `quay.io/calico/istio-pilot:v3.32.1 |
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 6 out of 6 changed files in this pull request and generated no new comments.
Suppressed comments (2)
src/new/data/ccImageLists.js:5
- The PR description says the v23.0.1 image list in this file is a placeholder and must be replaced before merging, but the code still contains a TODO and a manifest placeholder. Please replace this with the real v23.0.1 image-list output (or update the PR description if the placeholder is now considered acceptable).
// TODO(DOCS-3008): placeholder copied from the v23.0.0 list. Replace it with
// the v23.0.1 list once the release is in staging:
// curl -0 https://installer.calicocloud.io/manifests/<v23.0.1 manifest>/image-list
'v23.0.1 (latest)': `quay.io/calico/istio-pilot:v3.32.1
calico-cloud_versioned_docs/version-23-2/release-notes/index.mdx:17
- This sentence uses “crash looping”, but elsewhere in these release notes the term is written as “crash-loop”/“crash-looping”. Consider hyphenating for consistency and readability.
$[prodname] components keep resolving names for the whole upgrade, Guardian connects without crash looping, and the upgrade finishes.

Calico Cloud 23.0.1 fixes CI-2032, an upgrade failure that three customers have hit: PlaytechIMS, Insight Investment, and the Bain Capital POC. Upgrading to 23.0.0 moves the cluster DNS policy into the new calico-system tier while the allow-tigera tier remains in place at the same order with defaultAction Deny, so DNS to kube-dns hits the implicit deny in allow-tigera. Guardian cannot resolve the Calico Cloud address, it crash loops, and the upgrade never finishes. Where calico-node reaches the API server by domain name, calico-node, calico-apiserver, and calico-kube-controllers fail for the same reason.
Engineering is removing 23.0.0 as an available version to install and shipping 23.0.1 in its place, so the docs need to match.
Changes:
Two values are placeholders until the staging build is confirmed. Do not merge before they are replaced:
The second commit fixes two dead links that were failing the link check in make netlify, which blocked the main site deploy preview on every pull request, including this one:
Out of scope: the allow-tigera to calico-system rename and the missed breaking change note are DOCS-3007, in #2918.
Reviewers, the deploy preview is up. Please check these pages:
CI-2032: https://tigera.atlassian.net/browse/CI-2032
DOCS-3008: https://tigera.atlassian.net/browse/DOCS-3008