Skip to content
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

PVCs in EKS 1.24 stuck in Pending state #1766

Closed
ddl-lnarayanan opened this issue Sep 28, 2023 · 1 comment
Closed

PVCs in EKS 1.24 stuck in Pending state #1766

ddl-lnarayanan opened this issue Sep 28, 2023 · 1 comment
Labels
kind/bug Categorizes issue or PR as related to a bug.

Comments

@ddl-lnarayanan
Copy link

/kind bug

What happened?
Pods stuck in pending state, PVCs not getting bound with this error:

E0927 15:58:28.337744       1 driver.go:120] GRPC error: rpc error: code = Internal desc = Could not create volume "pvc-aa928776-736e-4b4f-9e5d-b19998b8df58": could not create volume in EC2: RequestCanceled: request context canceled
caused by: context canceled

The csi provisioner has this:
E0927 15:58:28.337564 1 controller.go:957] error syncing claim "aa928776-736e-4b4f-9e5d-b19998b8df58": failed to provision volume with StorageClass "gp3-encrypted": rpc error: code = DeadlineExceeded desc = context deadline exceeded

This seems to be similar to this issue #954

What you expected to happen?
Pod should run with PVC bound and EBS Volumes Created when provisioned dynamically

How to reproduce it (as minimally and precisely as possible)?

  • Upgrade to EKS 1.24
  • Use EC2 instance role and the role has AmazonEBSCSIDriverPolicy.

Anything else we need to know?:
I've multiple other clusters running using instance role where as AWS docs suggest using service accounts is the best option. Is using instance role no longer supported?

Environment

  • Kubernetes version (use kubectl version): 1.24
  • Driver version: 1.19

any guidance would be much appreciated!

@k8s-ci-robot k8s-ci-robot added the kind/bug Categorizes issue or PR as related to a bug. label Sep 28, 2023
@ddl-lnarayanan
Copy link
Author

Issue with CoreDNS add-on that was manifesting in a weird way. Fixing the coredns addon resolved this issue

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug.
Projects
None yet
Development

No branches or pull requests

2 participants