Repository navigation
Sofka on Linux gets stuck when connecting to EKS with MFA enabled #807
Replies: 2 comments 3 replies
|
Thanks for reporting! This is a bug, not a known limitation. sofka runs exec auth plugins non-interactively, so stdin is closed. The AWS CLI's MFA prompt doesn't read stdin though - it opens the terminal directly, and the terminal is owned by the TUI. So the prompt ends up hidden under the UI and the read never finishes, which is why it looks stuck instead of failing. It's not Linux specific either, macOS behaves the same. k9s has the same problem btw (derailed/k9s#2048), it was closed as not planned. I'd rather fix it here. Workaround for now: run this once in a shell and enter the MFA code aws eks get-token --cluster-name <cluster> --profile <profile>The AWS CLI caches the assumed role credentials in What I'll do:
Your sofka version, distro and the shape of the AWS profile ( |
|
Not working quite well can you recheck its getting struck again |
Uh oh!
There was an error while loading. Please reload this page.
When MFA is enabled for an AWS EKS connection, Sofka on Linux appears to get stuck during the connection flow.
Could Sofka handle this authentication flow more reliably, for example by prompting for the MFA code and continuing after verification, or by showing a clear error if MFA authentication is not supported?
Is this a known limitation? I can share the Sofka version, Linux distribution, and relevant logs if they would help diagnose it.
All reactions