[RFC] Authenticate in-cluster HTTP traffic - #6032
Draft
stefanprodan wants to merge 1 commit into
Draft
Conversation
stefanprodan
force-pushed
the
rfc-http-auth
branch
2 times, most recently
from
August 7, 2026 18:36
ad97ff1 to
a03e0f7
Compare
Signed-off-by: Stefan Prodan <stefan.prodan@gmail.com>
stefanprodan
force-pushed
the
rfc-http-auth
branch
from
August 7, 2026 18:46
a03e0f7 to
8c938d6
Compare
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
1 participant
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.
This RFC proposes a unified authentication mechanism for all in-cluster HTTP traffic between Flux components, based on Kubernetes bound service account tokens. Clients send a projected, audience-scoped token with each request, and
servers verify it using the Kubernetes TokenReview API, accepting only service accounts from the trusted
flux-systemnamespace.