-
-
Notifications
You must be signed in to change notification settings - Fork 7
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 call Kubernetes API from pod in cluster running on AWS EKS #37
Comments
What OTP version are you running on? Would it be possible for you to upgrade to 27? See: erlang/otp#7968 |
But yeah. After removing req, I might have to add back the fix for older versions of OTP |
I updated to OTP 27.0.1 and it's working now. Thank you! |
Reopening this as a reminder to add back the workaround for older versions removed in 1123909 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In my pod the
KUBERNETES_SERVICE_HOST
var is set to172.20.0.1
andKUBERNETES_SERVICE_PORT_HTTPS
is set to443
by default.When I try to call the API using the
FLAMEK8sBackend.K8sClient
I get the following errorAs I was trouble shooting this issue, one of the things I tried was reassigning the
KUBERNETES_SERVICE_HOST
tohttps://<id-omitted>.sk1.us-west-1.eks.amazonaws.com
, the endpoint I use when connecting to the API server externally. This worked!So the issue appears to be the default
KUBERNETES_SERVICE_HOST
setting of172.20.0.1
on EKS clusters.It's easy enough to workaround this issue but I'm unsure if this is a common problem for EKS users or if I am doing something wrong.
The text was updated successfully, but these errors were encountered: