-
Notifications
You must be signed in to change notification settings - Fork 808
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fargate node cannot run ebs-csi-controller #492
Comments
Yes, the driver depends on the metadata service (discussed here) #474. I agree with adding the annotation. Even if the metadata issue were overcome, there's no point running the driver on a fargate node where ebs volumes can't be attached. |
Thank you for your comment. I created a PR #496 . |
Is there any plans to attach ebs volumes to fargate nodes? We are running a heterogenous compute type in our eks cluster. Would really love this feature? @wongma7 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Is this the issue being used to track EBS on fargate + EKS? |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
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. |
/kind bug
What happened?
When the
ebs-csi-controller
pods are bound to fargate nodes, the pods stay inCrashLoopBackOff
status.What you expected to happen?
The
ebs-csi-controller
pods should successfully run.How to reproduce it (as minimally and precisely as possible)?
kube-system
namespace.Anything else we need to know?:
I'm going to submit a pull request which fixes
compute-type
of the deployment like this:Error log is:
Fargate node cannot access the EC2 instance metadata endpoint and cannot run the pod normally.
Environment
kubectl version
): v1.15.11-eks-af3cafThe text was updated successfully, but these errors were encountered: