feat: parse kubeconfig for bearer_token_file #677
Conversation
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.
As an user of the kubeclient gem
I want to configure my Kubeconfig::Client automatically to use a tokenFile from kubeconfig
So that my token is automatically refreshed and my client does not expire.
This PR adds parsing for tokenFile in the kubeconfig authinfo and automatically sets
auth_config[:bearer_token_file]in the client library. tokenFile will be prioritary over token entries if both are found.This feature makes the existing support for bearer_token_file (which allows for refreshing tokens) in this library easier to use.