-
Notifications
You must be signed in to change notification settings - Fork 537
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
Unable to provision volumes in iso-us-east-1 AWS region #1349
Comments
+1 |
Thank you for bringing this to our attention. We are investigating this issue. In the meantime, can you follow the log-collection steps linked here to provide us with debug logs? |
Getting logs from my actual environment is going to be tricky... let me see if I can figure out a way to reproduce things. |
Is there a reason why you can't use the managed add-on for EFS with your EKS cluster? The add-on is supported in ISO regions and fully compatible. The managed add-on already auto injects the custom CA bundle used in ISO regions. |
@whoix For unfortunate "reasons", we are unable to use EKS at the moment, so we are building our RKE2 clusters on EC2 instances w/ terraform and ansible. I believe the PR was merged yesterday, so this issue can probably be closed now. |
/kind bug
What happened?
Attempting to provision a volume fails because the provisioner does not trust the AWS TLS certificate. The following event is generated:
What you expected to happen?
The volume to be provisioned successfully.
How to reproduce it (as minimally and precisely as possible)?
Attempt to provision a volume in an AWS region that does not use a certificate issued by an authority in the standard CA certificate bundle.
Anything else we need to know?:
The certificate used by the AWS endpoint in my environment is not part of the standard CA bundle, so I need to mount my own CA trust bundle into the pods.
I suspect this would not longer be an issue if this PR is accepted: #1165
Environment
kubectl version
): 1.28.8+rke2r1Please also attach debug logs to help us better diagnose
The text was updated successfully, but these errors were encountered: