[RFC-0010] Add multi-tenancy lockdown for kubeconfig - #1284
Merged
matheuscscp merged 1 commit intoAug 17, 2025
Conversation
matheuscscp
reviewed
Aug 17, 2025
Adds new controller flag to enforce ServiceAccount usage in multi-tenant clusters where administrators need to lock down workload identity access: - --default-kubeconfig-service-account This flag complements the existing --default-service-account flag to provide multi-tenancy lockdown coverage for kubeconfig ServiceAccount fields in the HelmRelease API. Signed-off-by: cappyzawa <cappyzawa@gmail.com>
cappyzawa
force-pushed
the
rfc-0010-multi-tenancy-lockdown
branch
from
August 17, 2025 08:44
53c4643 to
82fae0c
Compare
71 tasks
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
2 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.
Part of: fluxcd/flux2#5465