Repository navigation
Dex Auth - #5
Merged
Merged
Dex Auth#5
Conversation
grudra7714
approved these changes
Oct 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
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.
What changed
Added proper user based authentication to the MCP server, instead of having a set user on deployment, it now uses Dex to authenticate with the Epinio server.
Why
The MCP was originally experimental and was meant for testing, this closes one of the last gaps to bring the system to a 1.0 state.
What to test
Possible regressions
Not being able to communicate through the MCP with Epinio via a dex user.
Checklist
make checkpasses (fmt-check, vet, lint, test)docs: document MCP per-user authentication docs#500
EPINIO_MCP_ELEVATED, reaches directly into Kubernetes and needs the standard-elevated RBAC)epinio/docs