Skip to content
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

Providing TLS certs for Typha and Node doesn't work out #3708

Open
untitled-sh opened this issue Jan 16, 2025 · 1 comment
Open

Providing TLS certs for Typha and Node doesn't work out #3708

untitled-sh opened this issue Jan 16, 2025 · 1 comment

Comments

@untitled-sh
Copy link

untitled-sh commented Jan 16, 2025

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

@tmjd
Copy link
Member

tmjd commented Jan 21, 2025

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.

If you're needing to configure those certificates with Calico then I'd suggest using https://docs.tigera.io/calico/latest/operations/certificate-management.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants