search

derailed / k9s

🐶 Kubernetes CLI To Manage Your Clusters In Style!
https://k9scli.io
Apache License 2.0
26.33k stars 1.65k forks source link

Add support of gimme-aws-creds #668

Open guanchzhou opened 4 years ago

guanchzhou commented 4 years ago




Is your feature request related to a problem? Please describe. Our clusters access is configured to use temporary AWS credentials generated with gimme-aws-creds tool which invoke Okta for getting a proper IAM role. Temp creds session is limited to 1 hour so after this time k9s exits with message: "Boom!! Lost K8s connection (10). Bailing out!."

Describe the solution you'd like Add setting to .k9s/config.yml file to let k9s know about using gimme-aws-creds so when next time session will end invoke gimme-aws-creds to have it updated.

k9s: clusters: superclustername: provider: gimme-aws-creds role: arn:aws:iam::ACCOUNT:role/ROLE

Invocation may be automated with call: gimme-aws-creds --roles arn:aws:iam::ACCOUNT:role/ROLE

85danf commented 1 year ago

I've been using (and loving!) k9s for a while now, in my new workplace we use kubeconfig files with user: exec: ... directives that run the aws client to get tokens - generally speaking would it be possible to support such auth schemes? i.e. make k9s 'understand' credentials that kubectl acquires externaly?