DOCS-2992: Remove remaining compliance feature prose from Calico Enterprise 3.24 and next - #2896
Merged
ctauchen merged 3 commits intoJul 31, 2026
Conversation
… next Second pass of the compliance removal, covering the prose the first pass left. In Calico Enterprise next and version-3.24-1: - Remove the Compliance component section, TOC entry, and intro/Manager mentions from the component architecture reference. - Remove the "Logs for compliance reporting" subsection from the observability overview. - Reword the audit-log docs (audit overview, Kubernetes audit logs) so they no longer describe compliance reports as a consumer. - Reword install and upgrade steps that told users to enable a Compliance resource, and drop the compliance install-option rows (options-install, default-install feature list). - Drop compliance from the Windows limitations table, the license read-only console list, and the log-storage prerequisite. Left in place: generic regulatory "compliance" wording unrelated to the feature, and references to components/fields that still ship (the LogStorage complianceReports retention field, the Compliance CR resource-configuration reference). Co-Authored-By: Claude Opus 4.8 (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. |
Contributor
There was a problem hiding this comment.
Pull request overview
Removes remaining documentation prose for the Calico Enterprise “Compliance” feature across both Enterprise next (calico-enterprise/) and the 3.24-1 versioned docs (calico-enterprise_versioned_docs/version-3.24-1/), aligning the docs with the earlier pass that removed compliance pages/navigation and related references.
Changes:
- Removes the Compliance component section (and related TOC entry) from the component architecture reference.
- Removes/rewords compliance-related language from observability/audit-log docs (including Elasticsearch overview and Kubernetes audit log docs).
- Updates install/upgrade flows, options tables, and limitations/licensing docs to remove compliance as an installable/visible feature.
Reviewed changes
Copilot reviewed 26 out of 26 changed files in this pull request and generated 7 comments.
Show a summary per file
| File | Description |
|---|---|
| calico-enterprise/reference/architecture/overview.mdx | Removes Compliance component prose and related mentions from the architecture overview. |
| calico-enterprise/operations/logstorage/create-storage.mdx | Removes compliance reports from storage prerequisites language. |
| calico-enterprise/operations/license-options.mdx | Removes Compliance from read-only console visibility list. |
| calico-enterprise/observability/kube-audit.mdx | Rewords Kubernetes audit logs content to remove compliance-report dependencies. |
| calico-enterprise/observability/elastic/overview.mdx | Removes the “Logs for compliance reporting” subsection. |
| calico-enterprise/observability/elastic/audit-overview.mdx | Removes compliance-report framing/screenshots and rewords required next steps. |
| calico-enterprise/installation/install-calico-enterprise-mke-4k.mdx | Removes compliance from optional enablement guidance during install. |
| calico-enterprise/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx | Removes compliance from optional Helm upgrade enablement instructions. |
| calico-enterprise/getting-started/install-on-clusters/windows-calico/limitations.mdx | Removes compliance-related limitations entry from Windows limitations table. |
| calico-enterprise/getting-started/install-on-clusters/kubernetes/quickstart.mdx | Removes compliance from optional custom-resources enablement step in quickstart. |
| calico-enterprise/getting-started/install-on-clusters/kubernetes/options-install.mdx | Removes Compliance from the operator API options table. |
| calico-enterprise/getting-started/install-on-clusters/kubernetes/helm.mdx | Removes compliance from optional Helm install enablement instructions. |
| calico-enterprise/_includes/content/_default-install.mdx | Removes compliance reporting from default install “You get…” table. |
| calico-enterprise_versioned_docs/version-3.24-1/reference/architecture/overview.mdx | Mirrors Compliance component removal in 3.24-1 architecture reference. |
| calico-enterprise_versioned_docs/version-3.24-1/operations/logstorage/create-storage.mdx | Mirrors storage prerequisite rewording for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/operations/license-options.mdx | Mirrors license read-only console list update for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/observability/kube-audit.mdx | Mirrors Kubernetes audit log rewording for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/observability/elastic/overview.mdx | Mirrors removal of compliance-report logging subsection for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/observability/elastic/audit-overview.mdx | Mirrors removal of compliance-report framing/screenshots for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/installation/install-calico-enterprise-mke-4k.mdx | Mirrors removal of compliance from optional enablement guidance for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx | Mirrors removal of compliance from optional Helm upgrade guidance for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/windows-calico/limitations.mdx | Mirrors Windows limitations table update for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/quickstart.mdx | Mirrors quickstart optional enablement wording update for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/options-install.mdx | Mirrors removal of Compliance from operator API options table for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/getting-started/install-on-clusters/kubernetes/helm.mdx | Mirrors Helm install optional enablement wording update for 3.24-1. |
| calico-enterprise_versioned_docs/version-3.24-1/_includes/content/_default-install.mdx | Mirrors removal of compliance reporting from default install table for 3.24-1. |
Comment on lines
+129
to
+131
| 1. Optional: Packet capture is an optional feature. To enable or maintain the enabled status, review the `values.yaml` file and set the flag to `enabled: true`. | ||
|
|
||
| If your `values.yaml` configuration does not include `compliance` or `packetCaptureAPI`, add them to the configuration and set to `enabled: true` | ||
| If your `values.yaml` configuration does not include `packetCaptureAPI`, add it to the configuration and set to `enabled: true` |
| 1. [Configure a storage class for Calico Enterprise](../../../operations/logstorage/create-storage). | ||
|
|
||
| 1. Optional: Compliance and packetcapture features are optional. To enable these features, review the `values.yaml` file and set the flag to `enabled: true`. In the next step, use this modified `values.yaml` for the Helm install. | ||
| 1. Optional: Packet capture is an optional feature. To enable it, review the `values.yaml` file and set the flag to `enabled: true`. In the next step, use this modified `values.yaml` for the Helm install. |
| ``` | ||
|
|
||
| 1. Optional: Compliance and packet capture features are optional. To enable these features during installation, download and review the custom-resources.yaml file. Uncomment the necessary CRs and use this custom-resources.yaml for installation. | ||
| 1. Optional: Packet capture is an optional feature. To enable it during installation, download and review the custom-resources.yaml file. Uncomment the necessary CRs and use this custom-resources.yaml for installation. |
| ## Big picture | ||
|
|
||
| Before installing $[prodname], you must configure persistent storage for flow logs, DNS logs, audit logs, and compliance reports. | ||
| Before installing $[prodname], you must configure persistent storage for flow logs, DNS logs, and audit logs. |
| | Networking | Default networking implementation based on your provider and platform. <br />Default IP pool/CIDR range. | | ||
| | Tiered network policy | Tiered network policy components. <br />Existing Kubernetes clusters are put in default tier.<br />$[prodname] components are secured with network policy. | | ||
| | User interface | the $[prodname] web console user interface (with a default of “no access outside the cluster”). | | ||
| | Logs and data | All nodes configured for log data collection using fluentdLog storage for a single node.<br />One instance of Elasticsearch and Kibana. | |
| | Networking | Default networking implementation based on your provider and platform. <br />Default IP pool/CIDR range. | | ||
| | Tiered network policy | Tiered network policy components. <br />Existing Kubernetes clusters are put in default tier.<br />$[prodname] components are secured with network policy. | | ||
| | User interface | the $[prodname] web console user interface (with a default of “no access outside the cluster”). | | ||
| | Logs and data | All nodes configured for log data collection using fluentdLog storage for a single node.<br />One instance of Elasticsearch and Kibana. | |
| ## Big picture | ||
|
|
||
| Before installing $[prodname], you must configure persistent storage for flow logs, DNS logs, audit logs, and compliance reports. | ||
| Before installing $[prodname], you must configure persistent storage for flow logs, DNS logs, and audit logs. |
…r removed pages The compliance component-resource reference (kept, since the components still ship) linked to Compliance API anchors that the first pass removed from the generated operator API reference. Unlink those anchors, keeping the configuration content as plain text. Add redirects for the compliance pages removed from Calico Enterprise 3.24: the compliance guide pages redirect to the release notes, and the compliance-reports reference pages and GlobalReport redirect to the resources reference index. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The TKG install page links to two VMware Tanzu Kubernetes Grid docs pages that now 502 the crawler after the Broadcom docs migration, failing the build's link check. Add docs.vmware.com to the link-check skip list, matching how the other vendor documentation sites (Mirantis, OpenShift, Red Hat) are handled. Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Second pass of the compliance removal (DOCS-2992). The first pass, which removed the compliance pages, navigation, cross-links, install references, and API reference, is already merged. This pass removes the remaining prose that describes the compliance feature, in Calico Enterprise next and version-3.24-1.
Removed or reworded:
Deliberately left in place:
Jira: https://tigera.atlassian.net/browse/DOCS-2992
For reviewers, representative changed pages are the component architecture reference and the observability overview.