DOCS-3009: Add deprecation lifecycle tables to the Calico Enterprise release notes - #2931
Merged
Merged
Conversation
✅ 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. |
Contributor
There was a problem hiding this comment.
Pull request overview
Adds “deprecation lifecycle” status tables to Calico Enterprise versioned release notes (3.21–3.24) so readers can see, at a glance, whether previously-deprecated features remain deprecated or have been removed, without needing to open individual feature pages.
Changes:
- Adds a 3-release rolling lifecycle table to the 3.24 and 3.23 release notes, placed after the existing Deprecated/removed bullet list.
- Introduces a new Deprecated and removed features section (with lifecycle table) to the 3.22 and 3.21 release notes.
Reviewed changes
Copilot reviewed 4 out of 4 changed files in this pull request and generated 4 comments.
| File | Description |
|---|---|
| calico-enterprise_versioned_docs/version-3.24-1/release-notes/index.mdx | Adds a deprecated/removed lifecycle table for 3.22–3.24. |
| calico-enterprise_versioned_docs/version-3.23-2/release-notes/index.mdx | Adds a deprecated/removed lifecycle table for 3.21–3.23. |
| calico-enterprise_versioned_docs/version-3.22-2/release-notes/index.mdx | Adds a “Deprecated and removed features” section with lifecycle table for 3.20–3.22. |
| calico-enterprise_versioned_docs/version-3.21-2/release-notes/index.mdx | Adds a “Deprecated and removed features” section with lifecycle table for 3.19–3.21. |
💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.
|
|
||
| | Feature | 3.22 | 3.23 | 3.24 | | ||
| | --- | --- | --- | --- | | ||
| | Compliance features | Deprecated | Deprecated | Removed | |
| | Aggregation API server | GA | GA | Deprecated | | ||
| | Application layer policy based on Envoy | GA | GA | Deprecated | | ||
| | L7 logging with Envoy | GA | GA | Deprecated | | ||
| | Compliance features | Deprecated | Deprecated | Deprecated | |
|
|
||
| | Feature | 3.20 | 3.21 | 3.22 | | ||
| | --- | --- | --- | --- | | ||
| | Compliance features | Deprecated | Deprecated | Deprecated | |
|
|
||
| | Feature | 3.19 | 3.20 | 3.21 | | ||
| | --- | --- | --- | --- | | ||
| | Compliance features | GA | Deprecated | Deprecated | |
ctauchen
force-pushed
the
docs-ce-deprecation-tables
branch
from
August 19, 2026 12:15
69045db to
24a3dcc
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.
Suppressed comments (2)
calico-enterprise_versioned_docs/version-3.24-1/release-notes/index.mdx:90
- In the deprecation table, "Compliance features" is marked as "Removed" in 3.24, but the bullet below says the compliance reporting feature was removed only from the $[prodname] web console. These statements conflict: either the table/YAML should not claim full removal, or the bullet should be updated to reflect full removal (if that’s what happened). Please confirm and make the wording/status consistent.
| Feature | 3.22 | 3.23 | 3.24 |
| --- | --- | --- | --- |
| Compliance features | Deprecated | Deprecated | Removed |
| Aggregation API server | GA | Deprecated | Deprecated |
| Application layer policy based on Envoy | GA | Deprecated | Deprecated |
data/feature-status.yaml:46
- This marks compliance features as removed in Calico Enterprise 3.24. However, the 3.24 release notes currently say the compliance reporting feature was removed only from the web console. If the backend feature still exists, this entry likely should remain "deprecated" (or similar) rather than "removed". Please confirm the actual product behavior and adjust the status accordingly.
- id: compliance-features
name: Compliance features
products:
calico-enterprise:
"3.19": ga
"3.20": deprecated
"3.24": removed
ctauchen
force-pushed
the
docs-ce-deprecation-tables
branch
from
August 19, 2026 12:21
24a3dcc to
c8a4f16
Compare
Contributor
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 (4)
calico-enterprise_versioned_docs/version-3.24-1/release-notes/index.mdx:100
- The bullets refer to the “aggregated API server”, but the feature name used in the table (and in this repo elsewhere) is “Aggregation API server” / “aggregation API server”. Using a different term here is likely to confuse readers and makes it harder to correlate the bullet with the table row.
* $[prodname] is moving the `projectcalico.org/v3` API from the aggregated API server to native Kubernetes CRDs.
Both mechanisms will be supported until native v3 CRDs are compatible with all supported platforms, after which the aggregated API server will be removed.
calico-enterprise_versioned_docs/version-3.23-2/release-notes/index.mdx:172
- This bullet says “aggregated API server”, but the feature name in the table is “Aggregation API server” and the term used elsewhere in the docs is “aggregation API server”. Aligning terminology will make the bullet clearly map to the table row.
* $[prodname] is moving the `projectcalico.org/v3` API from the aggregated API server to native Kubernetes CRDs. Both mechanisms will be supported until native v3 CRDs are compatible with all supported platforms, after which the aggregated API server will be removed.
calico-enterprise_versioned_docs/version-3.24-1/release-notes/index.mdx:88
- The table marks Compliance reporting as “Removed” in 3.24, but the bullet below says it was removed only from the $[prodname] web console. These two statements conflict; please confirm whether the feature is fully removed in 3.24 or only the UI portion, and adjust the table wording/status accordingly.
| Compliance reporting | Deprecated | Deprecated | Removed |
data/feature-status.yaml:46
- This entry records Compliance reporting as
removedin Calico Enterprise 3.24, but the 3.24 release notes bullet says it was removed only from the web console. Please confirm the actual removal scope and adjust this status (or the release notes wording) so the lifecycle tables don’t overstate removal.
- id: compliance-reporting
name: Compliance reporting
products:
calico-enterprise:
"3.19": ga
"3.20": deprecated
"3.24": removed
The release notes record a deprecation once, in the release it happens, and often not at all. The Fortinet integration has been deprecated on every one of its pages since 3.18 and appears in no release notes. This adds a Deprecated and removed features section to the 3.21 and 3.22 release notes, gives the 3.23 and 3.24 sections a table, and matches the open source sections added in 2929. Rows cover the five features that carry a deprecation admonition on their pages: the Fortinet integration, compliance features, application layer policy based on Envoy, L7 logging with Envoy, and the aggregation API server. Changes: - Add the section to the 3.21 and 3.22 release notes, each with a table covering a rolling window of three releases. - Add the table to the 3.23 and 3.24 sections, and move their existing bullets into a Deprecated and removed features in this release subsection. - Record all five deprecations in data/feature-status.yaml, and add the Calico Enterprise release line to the existing aggregation API server entry. The tables in this pull request match what that file generates. Compliance features read Removed in 3.24 on the evidence of the docs, where the compliance reports reference section is deleted and the compliance section drops from six pages to three. The 3.24 release note claims removal from the web console only. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
ctauchen
force-pushed
the
docs-ce-deprecation-tables
branch
from
August 19, 2026 12:26
c8a4f16 to
4f7dbd0
Compare
Contributor
There was a problem hiding this comment.
Pull request overview
Copilot reviewed 5 out of 5 changed files in this pull request and generated no new comments.
Suppressed comments (2)
data/feature-status.yaml:46
- This entry marks compliance reporting as "removed" in 3.24, but the 3.24 release notes text currently states removal only from the web console. Please confirm the actual scope; if the backend feature still exists, the status here likely shouldn’t be "removed" (or the release note wording should be updated to reflect full removal).
products:
calico-enterprise:
"3.19": ga
"3.20": deprecated
"3.24": removed
calico-enterprise_versioned_docs/version-3.24-1/release-notes/index.mdx:90
- The compliance reporting lifecycle is inconsistent within this page: the table marks it as "Removed" in 3.24, but the bullet below says it was removed only from the web console. Please confirm whether the feature is fully removed in 3.24; then update either the table (and its source data) or the bullet text so they agree on the scope of removal.
| Feature | 3.22 | 3.23 | 3.24 |
| --- | --- | --- | --- |
| Compliance reporting | Deprecated | Deprecated | Removed |
| Aggregation API server | GA | Deprecated | Deprecated |
| Application layer policy based on Envoy | GA | Deprecated | Deprecated |
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.
The release notes record a deprecation once, in the release it happens, and often not at all. The Fortinet integration has been deprecated on every one of its pages since 3.18 and appears in no release notes. This adds a Deprecated and removed features section to the 3.21 and 3.22 release notes, gives the 3.23 and 3.24 sections a table, and matches the open source sections added in #2929.
Rows cover the five features that carry a deprecation admonition on their pages: the Fortinet integration, compliance features, application layer policy based on Envoy, L7 logging with Envoy, and the aggregation API server.
Changes:
The 3.21 and 3.22 sections have a table but no bulleted subsection, because neither release deprecated or removed anything new.
Compliance features read Removed in 3.24 on the evidence of the docs, where the compliance reports reference section is deleted and the compliance section drops from six pages to three. The 3.24 release note claims removal from the web console only, so please confirm whether the backend feature is also gone.
DOCS-3009: https://tigera.atlassian.net/browse/DOCS-3009
Deploy preview, 3.24 release notes, which has the largest table: https://deploy-preview-2931--tigera.netlify.app/calico-enterprise/3.24/release-notes