Kubeseal not working on EKS IPv6 CLuster about sealed-secrets HOT 8 CLOSED

sorry @Vinaum8, trying to reproduce it. I will come back as soon as possible. Thanks for your time

from sealed-secrets.

Simply add

command:
          - controller
          - --listen-addr
          - '[::]:8080'
          - --listen-metrics-addr
          - '[::]:8081'

to the values of your helm chart and voilà :)

from sealed-secrets.

Not sure what's your issue there, but in my case I found it easier to enable the ingress and use kubeseal --cert https://example.com/v1/cert.pem instead of working with the service directly, especially since most of my users don't have access to the kubernetes API

from sealed-secrets.

@alvneiayu Do you have any suggestions or alternatives for this problem?

from sealed-secrets.

@Vinaum8 Did that configuration worked for you?

from sealed-secrets.

@agarcia-oss yes, my kube seal server is listen on ipv6 address.
Thanks @fayak

HTTP server serving on [::]:8080 HTTP metrics server serving on [::]:8081

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`

from sealed-secrets.

Hmmmm, i'll test this.

from sealed-secrets.

Not sure what's your issue there, but in my case I found it easier to enable the ingress and use kubeseal --cert https://example.com/v1/cert.pem instead of working with the service directly, especially since most of my users don't have access to the kubernetes API

Man, i use this approach and works for me!

Add Command and Create Ingress!

Thanks @fayak

from sealed-secrets.