aws-efs-csi-driver
aws-efs-csi-driver copied to clipboard
kubernetes-sigs
Use secret or env to pass AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY in non-eks cluster to setup the driver permission
Is your feature request related to a problem? Please describe. I'm always frustrated when I try to deploy efs-csi to a self-managed k8s cluster. So far there is one way to grant driver IAM permission by using an IAM instance profile. However, I have no permission to set this profile so I wanna to use my AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as the credentials.
Describe the solution you'd like in detail What I have tried is to pass AWS_ACCESS_KEY_ID and AWS_SECRET_ACCESS_KEY as env parameters for containers efs-plugin and csi-provisioner (both in controller and ds), I'm not sure this is the right way to achieve my goal, but it works.
Describe alternatives you've considered If I'm doing it the right way, I'd like to create PR and modify the chart files to support this feature. Or, make some changes to let csi support a secret like what IAM ARN is.
Additional context No
The Kubernetes project currently lacks enough contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle stale - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues.
This bot triages un-triaged issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Mark this issue as fresh with
/remove-lifecycle rotten - Close this issue with
/close - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle rotten
Second this, I have to use a non-eks cluster but I want to use shared filesystems with the EFS driver (rather than just non-shared EBS filesystems)
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied - After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied - After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closed
You can:
- Reopen this issue with
/reopen - Mark this issue as fresh with
/remove-lifecycle rotten - Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
@k8s-triage-robot: Closing this issue, marking it as "Not Planned".
In response to this:
The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.
This bot triages issues according to the following rules:
- After 90d of inactivity,
lifecycle/staleis applied- After 30d of inactivity since
lifecycle/stalewas applied,lifecycle/rottenis applied- After 30d of inactivity since
lifecycle/rottenwas applied, the issue is closedYou can:
- Reopen this issue with
/reopen- Mark this issue as fresh with
/remove-lifecycle rotten- Offer to help out with Issue Triage
Please send feedback to sig-contributor-experience at kubernetes/community.
/close not-planned
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.
