You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Tried using helm values.yaml config parameters get's stuck from kube-system/coredns and calico-apiserver since container creating.
Any hint for me please ? To better qualify, what should I provide ? Any more detailed documentation, how I could provide TLS certs to Typha-Server w/ local CA as issuer ? Best would be if I could use existing secret, but for now Im even stuck w/ fresh mTLS certs specifically for Typha & Node.
Thanks a lot in advance
The text was updated successfully, but these errors were encountered:
If you're following the enterprise documentation then that should mean you're using the Calico Enterprise product, please reach out to your customer support contact and they should be able to help you navigate certificate configuration options.
Tried using your documentation (https://docs.tigera.io/calico-enterprise/latest/operations/comms/typha-node-tls) w/ several PEM formats doesn't worked out. After the apply, Port 5473 is not connectable anymore, although the pods are running w/ correct secrets & config maps.
Tried using helm values.yaml config parameters get's stuck from kube-system/coredns and calico-apiserver since container creating.
Any hint for me please ? To better qualify, what should I provide ? Any more detailed documentation, how I could provide TLS certs to Typha-Server w/ local CA as issuer ? Best would be if I could use existing secret, but for now Im even stuck w/ fresh mTLS certs specifically for Typha & Node.
Thanks a lot in advance
The text was updated successfully, but these errors were encountered: