Skip to content

DOCS-2992: Add a pre-upgrade step to delete the Compliance resource #2905

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
caseydavenport wants to merge 3 commits into
base: main
Choose a base branch
from
Open

DOCS-2992: Add a pre-upgrade step to delete the Compliance resource #2905

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
e77a1d8
Add Compliance removal step to Enterprise upgrade docs
caseydavenport Aug 4, 2026
5cbfd21
Add the Compliance removal step to the 3.24-1 upgrade docs
caseydavenport Aug 4, 2026
890d1bc
Revert "Add the Compliance removal step to the 3.24-1 upgrade docs"
caseydavenport Aug 5, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 12 additions & 0 deletions ...getting-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/helm.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -38,6 +38,18 @@ the upgrade.

If your cluster has Windows nodes and uses custom TLS certificates for log storage then, prior to upgrade, prepare and apply new certificates for [log storage](../../../../operations/comms/index.mdx) that include the required service DNS names.

### Compliance

The Compliance feature is removed in this release. Delete the Compliance resource before you upgrade, so that Kubernetes garbage collects the compliance deployments, service accounts, and RBAC that it owns.

```bash
kubectl delete compliance tigera-secure
```

If you manage $[prodname] resources with GitOps tooling, remove the Compliance resource from your source manifests as well. Otherwise the tooling recreates it after you upgrade.

If you receive an error indicating the resource or resource type does not exist, Compliance was not installed in your cluster. You can safely ignore the error and proceed.

### Upgrade OwnerReferences

If you do not use OwnerReferences on resources in the projectcalico.org/v3 API group, you can skip this section.
Expand Down
12 changes: 12 additions & 0 deletions ...ing-started/upgrading/upgrading-enterprise/kubernetes-upgrade-tsee/operator.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -45,6 +45,18 @@ have their reclaim policy set to [retain data](https://kubernetes.io/docs/tasks/
Retaining data is only recommended for users that use a valid Elastic license. Trial licenses can get invalidated during
the upgrade.

### Compliance

The Compliance feature is removed in this release. Delete the Compliance resource before you upgrade, so that Kubernetes garbage collects the compliance deployments, service accounts, and RBAC that it owns.

```bash
kubectl delete compliance tigera-secure
```

If you manage $[prodname] resources with GitOps tooling, remove the Compliance resource from your source manifests as well. Otherwise the tooling recreates it after you upgrade.

If you receive an error indicating the resource or resource type does not exist, Compliance was not installed in your cluster. You can safely ignore the error and proceed.

### Upgrade OwnerReferences

If you do not use OwnerReferences on resources in the projectcalico.org/v3 API group, you can skip this section.
Expand Down
12 changes: 12 additions & 0 deletions ...enterprise/getting-started/upgrading/upgrading-enterprise/openshift-upgrade.mdx
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,6 +48,18 @@ have their reclaim policy set to [retain data](https://kubernetes.io/docs/tasks/
Data retention is recommended only for users that have a valid Elasticsearch license. (Trial licenses can be invalidated
during upgrade).

### Compliance

The Compliance feature is removed in this release. Delete the Compliance resource before you upgrade, so that Kubernetes garbage collects the compliance deployments, service accounts, and RBAC that it owns.

```bash
oc delete compliance tigera-secure
```

If you manage $[prodname] resources with GitOps tooling, remove the Compliance resource from your source manifests as well. Otherwise the tooling recreates it after you upgrade.

If you receive an error indicating the resource or resource type does not exist, Compliance was not installed in your cluster. You can safely ignore the error and proceed.

### Upgrade OwnerReferences

If you do not use OwnerReferences on resources in the projectcalico.org/v3 API group, you can skip this section.
Expand Down