Extend documentation to embed Vault into kubeconfig - #30974
Merged
Conversation
|
|
schavis
approved these changes
Jul 16, 2025
schavis
enabled auto-merge (squash)
July 16, 2025 23:48
Erfankam
pushed a commit
to Erfankam/vault
that referenced
this pull request
Sep 1, 2025
Co-authored-by: Sarah Chavis <62406755+schavis@users.noreply.github.com>
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
This PR extends the documentation on how to dynamically generate Kubernets tokens by Vault in a quiet user friendly way.
It solves #30973 by converting the token coming from Vault via
jqand inject it directly into the context ofkubectl. By this, the whole token generation mechanism can be hidden from the user by including everything needed within thekubeconfigfile itself.