summaryrefslogtreecommitdiffstats
path: root/kubernetes/so/components/so-etsi-nfvo-ns-lcm/templates/ingress.yaml
diff options
context:
space:
mode:
authorSylvain Desbureaux <sylvain.desbureaux@orange.com>2020-10-26 13:34:18 +0100
committerSylvain Desbureaux <sylvain.desbureaux@orange.com>2020-10-26 17:48:44 +0100
commit80a32b94ca05c392d49a0abaeeec27e859358633 (patch)
tree92cbdb07bb14cb1d7585a1845c60a48aad63c00e /kubernetes/so/components/so-etsi-nfvo-ns-lcm/templates/ingress.yaml
parent951290ba262db65ac7f6cdfb659987cb394916ee (diff)
[COMMON] Add TLS for Ingress configuration
Instead of setting TLS termination at POD level, it may be interesting to terminate it at Ingress level. This patch add the ability to do that using "Ingress" templates. In order to achieve it, you need to configure it this way in `values.yaml`: ```yaml ingress: enabled: false service: - baseaddr: 'my-endpoint' name: 'my-service' port: 8080 config: tls: secret: my-service-ingress-certs ``` Secret (here `my-service-ingress-certs`) must follow Kubernetest `kubernetes.io/tls` type: https://kubernetes.io/docs/concepts/services-networking/ingress/#tls Issue-ID: SO-3078 Issue-ID: SO-3237 Issue-ID: OOM-2609 Signed-off-by: Sylvain Desbureaux <sylvain.desbureaux@orange.com> Change-Id: I76c0929d53289a581bc26d0d03cc8b9bd72d0fd1
Diffstat (limited to 'kubernetes/so/components/so-etsi-nfvo-ns-lcm/templates/ingress.yaml')
0 files changed, 0 insertions, 0 deletions