boltops-tools / boltops-tools/aws-mfa-secure
K8s integration with IAM Role
- Dominant language
- Ruby
- Stars
- 25
- Forks
- 5
- PR merge metrics
- No merged PRs in 30d
Description
When running `aws eks update-kubeconfig` with `--role-arn` new entry created under `.kube/config`. which contains the following:
```yaml
- name: arn:aws:eks:eu-west-1:123456789:cluster/xxx
user:
exec:
apiVersion: client.authentication.k8s.io/v1alpha1
args:
- --region
- eu-west-1
- eks
- get-token
- --cluster-name
- yyy
- --role
- arn:aws:iam::123456789:role/admin
command: aws
```
Any kubectl command or IDE for k8s failed to run due to the fact that `alias aws="aws-mfa-secure session"` contains a space, this caused the kubeconfig to fail the command.
My questions are -
1. Do you have any workaround?
2. Can you add another command to skip the `session` usage? ( e.g `aws-mfa-secure` without the `session` )
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reproducing the failure with the named aws-mfa-secure session command, the AWS EKS update-kubeconfig example, and the alias containing a space. Trace the CLI entry point for session handling; done means a supported invocation works with the generated kubeconfig while existing session behavior remains intact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- aws, kubernetes, ruby
- Domain
- authentication, cli, cloud
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100