-
Notifications
You must be signed in to change notification settings - Fork 807
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
Can't create volume with full-private cluster #889
Comments
@AndyXiangLi I guess this error is caused by full-private clusters. I have tried to deploy in a public subnet cluster, and CSI is worked. These endpoints are created by EKSCTL. |
I'm about to configure a cluster in similar manner, so I'm interested in the solution to this. |
@AndyXiangLi |
Thanks, I will close this issue then |
@AndyXiangLi: 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?
EBS CSI can't create volume with full-private EKS cluster.
Refer docs: https://docs.aws.amazon.com/eks/latest/userguide/ebs-csi.html
I got some error logs:
my eks yaml:
Default VPC endpoint created by eksctl
What you expected to happen?
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?:
Environment
kubectl version
):The text was updated successfully, but these errors were encountered: