-
Notifications
You must be signed in to change notification settings - Fork 666
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
Kubeseal not working on EKS IPv6 CLuster #1446
Comments
@alvneiayu Do you have any suggestions or alternatives for this problem? |
sorry @Vinaum8, trying to reproduce it. I will come back as soon as possible. Thanks for your time |
Simply add
to the values of your helm chart and voilà :) |
@Vinaum8 Did that configuration worked for you? |
@agarcia-oss yes, my kube seal server is listen on ipv6 address.
But, my connection beetwen kubeseal client and kubeseal server not working. `$ kubeseal < secret.yaml > sealed-secret.yaml error: cannot fetch certificate: error trying to reach service: dial tcp [2600:1f1e:82a:9d05:df4f::b]:8080: connect: connection timed out` |
Not sure what's your issue there, but in my case I found it easier to enable the ingress and use |
Hmmmm, i'll test this. |
Man, i use this approach and works for me! Add Command and Create Ingress! Thanks @fayak |
Which component:
SERVER:
Helm chart: https://bitnami-labs.github.io/sealed-secrets/sealed-secrets
Chart Version: 2.14.1
Container Image: docker.io/bitnami/sealed-secrets-controller:v0.24.5
CLIENT:
kubeseal version: v0.24.5
Describe the bug
well, i tried generate the sealed secrets with kubeseal binary version 0.24.5 and the connection start and finalize with message:
error: cannot fetch certificate: error trying to reach service: dial tcp [2600:1f1e:82a:9d05:25f3::a]:8080: connect: connection timed out
this same kubeseal (server and client version) installed in other clusters with ipv4 work fine.
I had this same error with rabbitmq maganement port and metrics port and the solution was to change the config file in the line of listen port.
From: 0.0.0.0
To: ::
Is there anything i can do?
To Reproduce
Wih EKS Cluster IPV6.
Install Helm Chart Version
Install Binary Version
Generate Secret.
Expected behavior
[A clear and concise description of what you expected to happen.](error: cannot fetch certificate: error trying to reach service: dial tcp [CLUSTERIP]:8080: connect: connection timed out)
Version of Kubernetes: 1.28
kubectl version
:The text was updated successfully, but these errors were encountered: