Skip to content

Remove the deprecated Compliance feature#4924

Draft
caseydavenport wants to merge 4 commits into
tigera:masterfrom
caseydavenport:casey-remove-compliance
Draft

Remove the deprecated Compliance feature#4924
caseydavenport wants to merge 4 commits into
tigera:masterfrom
caseydavenport:casey-remove-compliance

Conversation

@caseydavenport

Copy link
Copy Markdown
Member

Removes the deprecated Compliance feature from the operator. Deletes the Compliance CRD and its API types, the compliance controller, the compliance rendering, and the compliance-benchmarker image, and drops the compliance integration from the manager controller (license check, watch, Voltron compliance env vars) along with the now-dead compliance network-policy rules in guardian, dex and linseed.

The compliance data API is kept - the LogStorage retention fields and Tenant data types - since historical compliance data is still served from storage.

Removed the deprecated Compliance feature.

Delete the Compliance CRD and its API types, the compliance controller, the
compliance rendering, and the compliance-benchmarker image. Drop the compliance
integration from the manager controller (license check, watch, Voltron
compliance env vars) and the now-dead compliance network-policy rules in
guardian, dex and linseed.

Keep the compliance data API - LogStorage retention fields and Tenant data
types - since Linseed still serves historical compliance data.

Regenerated deepcopy.
Drop the Compliance CR test cases and the compliance config plumbing from the
manager and manager-controller tests, and the compliance override entries from
the components test. Also discard the now-unused license value in the manager
controller (the fetch stays for its not-found validation).
Drop ComponentComplianceBenchmarker from the gen-versions template so the
generated enterprise.go matches. Remove the compliance rules from the rendered
network-policy golden files (dex, manager, guardian, linseed) and drop
tigera-compliance from the DNS / node-local-DNS namespace selectors. Adjust the
manager non-cluster-host egress count now that the compliance egress rule is gone.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants