Skip to content

Move multi-tenant certificate manager behavior to an Enterprise package - #5222

Merged
caseydavenport merged 1 commit into
tigera:masterfrom
caseydavenport:casey-certmanager-tenancy
Aug 20, 2026
Merged

Move multi-tenant certificate manager behavior to an Enterprise package#5222
caseydavenport merged 1 commit into
tigera:masterfrom
caseydavenport:casey-certmanager-tenancy

Conversation

@caseydavenport

@caseydavenport caseydavenport commented Aug 19, 2026

Copy link
Copy Markdown
Member

Description

Another variant-gating split. The base certificate manager no longer knows what a tenant is:

  • the CA secret name is now an option on the constructor, instead of a tenant argument the constructor inspects
  • trusted bundle creation takes the configmap name as a parameter, which lets the multi-tenant branch in the bundle loader be deleted rather than relocated
  • a new Enterprise package wraps the base one and supplies the per-tenant CA secret name and the public bundle name

No behavior change. Enterprise controllers go through the new package and get the same CA secret and configmap names as before.

One thing for review: the CA secret name option is exported, so nothing structurally stops a Calico caller from pointing it at the tenant CA. That seemed like a better trade than keeping the tenant type in the base package, but say the word if you'd rather pay for a narrower mechanism.

Related: CORE-13395

None

The base certificate manager takes the CA secret and bundle names as parameters
rather than deriving them from a tenant.
@caseydavenport
caseydavenport merged commit 2d8b72a into tigera:master Aug 20, 2026
7 of 11 checks passed
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.

3 participants