You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
So this is a long shot, but I thought you may had the same issue at some point.
I have created the cluster based on the repo instructions, everything is working, I'm able to connect to the Bastion server and I'm able to manage the kubernetes cluster.
But I'm having a problem when I tried to configure the EBS CSI driver and I hope you had the same issue or maybe I'm missing something and I need a fresh pair of eyes.
I'm following the AWS instructions to install the EBS CSI driver.
I didn't want to think too much, so I use the secret to give the driver permissions to AWS.
I used the default helm chart installation.
The pods are started correctly and made a simple test of putting the wrong access_key to get the error on the logs.
I'm getting this error when I tried to create a pvc:
ebs.csi.aws.com_ebs-csi-controller-xxxxxx failed to provision volume with StorageClass "gp2-sc": rpc error: code = DeadlineExceeded desc = context deadline exceeded
It looks like a networking issue. I added an inbound rule to open from All to 0.0.0.0/0 just for testing, but I had the same result.
Any suggestion?
Thanks
The text was updated successfully, but these errors were encountered:
So this is a long shot, but I thought you may had the same issue at some point.
I have created the cluster based on the repo instructions, everything is working, I'm able to connect to the Bastion server and I'm able to manage the kubernetes cluster.
But I'm having a problem when I tried to configure the EBS CSI driver and I hope you had the same issue or maybe I'm missing something and I need a fresh pair of eyes.
I'm following the AWS instructions to install the EBS CSI driver.
I didn't want to think too much, so I use the secret to give the driver permissions to AWS.
I used the default helm chart installation.
The
pods
are started correctly and made a simple test of putting the wrongaccess_key
to get the error on the logs.I'm getting this error when I tried to create a
pvc
:It looks like a networking issue. I added an inbound rule to open from
All to 0.0.0.0/0
just for testing, but I had the same result.Any suggestion?
Thanks
The text was updated successfully, but these errors were encountered: