-
Notifications
You must be signed in to change notification settings - Fork 543
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
GRPC error: rpc error: code = Internal desc = Failed to fetch Access Points or Describe File System: List Access Points failed: RequestCanceled: request context canceled caused by: context deadline exceeded #1290
Comments
@RyanStan any follow up here? |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues. This bot triages un-triaged issues according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
@jonassteinberg1 , hello, I'm facing the same issue even with the latest addon version. Did you managed to resolve that ? |
I had a similar problem, during the checking process I added a netshoot-sidecar container to efs-csi-controller, went inside the pod and checked and found out that it was a dns issue, due to a misconfiguration of coredns. I hope this idea can help you. |
@SimonMachine would you mind explaining what the DNS issues were and how you fixed these? |
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:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle rotten |
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:
You can:
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:
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-sigs/prow repository. |
/kind bug
What happened?
Documentation does not specify that this driver and its resultant workflows can only be used on EKS. Much of the documentation is oriented towards EKS, because no one self-hosts anymore, but none of it says EKS must be used. That being the case I have attempted to implement this on self-managed ec2 instances. I have followed the installation instructions, except I do not have an OIDC provider enabled. Is one absolutely required?
Should be simple enough -- some type of access problem. Okay:
fs-06865cae821d34e69
and this is called correctly in my storage class manifest.sudo mount -t efs -o tls,accesspoint=fsap-0515214d4fe7bdac7 fs-06865cae821d34e69:/ efs
not even sure if this is needed?aws efs anything
from all my cluster instances via boto3*.*
so all permissions, in other words:What you expected to happen?
dynamic provisioning
How to reproduce it (as minimally and precisely as possible)?
Anything else we need to know?:
The debug script
results/efs_utils_state_dir
are:but when I do an ls on
/var/run/efs
I get:Environment
kubectl version
):1.7.6
Please also attach debug logs to help us better diagnose
debug logs attached
results.tgz
The text was updated successfully, but these errors were encountered: