Support multiple TLS certificates via SNI
See original GitHub issueAmbassador supports a single TLS certificate but I need to support multiple TLS certificates where we use different domains for different types of services.
*.kubernaut.io
is for Kubernaut
scout.datawire.io
is needed for another service.
We have other services coming down the pipeline that will also need to be able to be under a different domain and therefore require another TLS wildcard certificate.
Issue Analytics
- State:
- Created 6 years ago
- Reactions:10
- Comments:10 (6 by maintainers)
Top Results From Across the Web
Application Load Balancers Now Support Multiple TLS ...
Today we're launching support for multiple TLS/SSL certificates on Application Load Balancers (ALB) using Server Name Indication (SNI).
Read more >Support multiple TLS certificates via SNI · Issue #153 - GitHub
Ambassador supports a single TLS certificate but I need to support multiple TLS certificates where we use different domains for different types of...
Read more >Get multiple TLS/SSL certificates using SNI automation
On the automation request page, enter the common name and server name that you want the certificate to secure based on the automation...
Read more >Now supporting Server Name Indication (SNI) and Multiple TLS
Server Name Indication (SNI) support, a feature that allows the configuration of multiple TLS certificates where different domain names are used.
Read more >SNI Certificate in SSL/TLS: All You Need to Know
SNI is an extension to the SSL/TLS protocol that allows multiple SSL/TLS certificates to be hosted on a single IP address. This is...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Hi @plombardi89 , i see that the ticket you mention has been closed on Dec 2017 , and envoy support tls: added SNI support. from version 1.5 ( https://www.envoyproxy.io/docs/envoy/latest/intro/version_history#id1 ) Is there and estimated for this, or is even in the roadmap? we really need this feature to work with several certificates.
SNI is a high priority item (we’re doing a bunch of internal work on a branch which is a precursor to SNI, among other things). In the meantime, you can run multiple ambassadors (see https://www.getambassador.io/reference/running#multiple-ambassadors-in-one-cluster) and give each ambassador a unique secret.