Move the tenant secrets controller into its own package - #5193
Merged
caseydavenport merged 1 commit intoAug 14, 2026
Conversation
It only runs in multi-tenant mode, so keeping it separate from the cluster CA controller lets the whole package be dropped on the OSS side.
Brian-McM
approved these changes
Aug 14, 2026
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
3 participants
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.
Description
Pure move, split out of #5170 to keep that review smaller. The tenant secrets controller only runs in multi-tenant mode, so it gets its own package rather than sharing one with the cluster CA controller. That way the whole package can be dropped on the OSS side instead of picking a file out of a shared one.
No behaviour change - same controller, same wiring, new package.
Release Note