-
-
Notifications
You must be signed in to change notification settings - Fork 46
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
hostname issues #230
Comments
This works as well as a workaround
|
Yes this is known. See #203 and the migration doc: https://hexdocs.pm/k8s/migrations.html#local-clusters-and-tls-hostname-verification An option might be helpful, yes. |
Thanks @mruoss , I came from the latest in bonny and it just stopped working from the latest upgrade. |
Hi, I'm upgrading from v1.1 to v2.4 and I get the exact same issue, except I'm running EKS (1.27), so I expect TLS certs to be good, I'm creating connections via |
Yeah this is still not very clear to me why HTTPoison let this skip and Mint doesn't. You probably know this but you can fix it by using |
Note that you can remove your |
with the upgrade
I have to add
to the kubeconfig context.
Minikube for example exposes the cert, but doesn't have the hostname for verification.
this is the error
Would a option being passed to
K8s.Conn.from_file
be helpful?The text was updated successfully, but these errors were encountered: