[caas] no way to specify cert and key for ingress TLS termination via k8s secrets
Bug #1843260 reported by
Dmitrii Shcherbakov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Canonical Juju |
Fix Released
|
High
|
Yang Kelvin Liu | ||
Bug Description
Kubernetes allows specifying TLS cert and key for ingress TLS termination via Secrets.
https:/
Port 443 is used as a front-end port and multiplexing is done via hostnames and SNI.
The aim is to provide secure connections between external clients and an ingress controller.
Revision history for this message
| Ian Booth (wallyworld) wrote | #1 |
| Changed in juju: | |
| milestone: | none → 2.7-beta1 |
| assignee: | nobody → Yang Kelvin Liu (kelvin.liu) |
| importance: | Undecided → High |
| status: | New → Triaged |
Revision history for this message
| Yang Kelvin Liu (kelvin.liu) wrote | #2 |
| Changed in juju: | |
| status: | Triaged → In Progress |
| status: | In Progress → Fix Committed |
| Changed in juju: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
We are currently implementing support for k8s secrets. This will appear in the 2.7 edge snap for testing.