Skip to content

(Automatic) Approach to reload changes to ~/.kube/config (for updated authentication) #3607

@MaicoTimmerman

Description

@MaicoTimmerman

I’d like to have k9s pick up changes to my .kube/config, specifically updated authentication (id-token). I’m using a plugin to trigger refresh of authentication for a context, however, k9s doesn’t pick that up, because the API Server client is cached.

I’ve been taking a look at the code to see if I could contribute the feature, and I’m looking for some guidance here. The places where the active API connection and context are stored seem to be scattered, thus it doesn’t seem very straight forward to achieve this.

Is your feature request related to a problem? Please describe.
Context's that have expired authentication, can not be refreshed using a plugin. k9s doesn't pick up the new tokens.

Describe the solution you'd like
Open for suggestions here!

Describe alternatives you've considered
Restart of k9s.

Additional context
Happy to try and contribute!

Metadata

Metadata

Assignees

No one assigned

    Labels

    questionFurther information is requested

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions