From 779c51275f30927dbd783e878e064124cfa0e609 Mon Sep 17 00:00:00 2001 From: Cedric Kring <39853520+cedrickring@users.noreply.github.com> Date: Wed, 13 Nov 2019 17:14:25 +0100 Subject: [PATCH] Document secretName support for Ingress TLS (#308) * Add documentation on how to configure the Ingress with the operator This commit adds a new section to 'Configuring the CRD' with examples on how to disable the ingress and how to add a tls certificate to it. Issue #307 Signed-off-by: Cedric Kring * Move TLS documentation to "Accessing the Jaeger Console (UI)" Signed-off-by: Cedric Kring * Change "to a secret" to "of a secret" Signed-off-by: Cedric Kring --- content/docs/next-release/operator.md | 12 ++++++++++++ 1 file changed, 12 insertions(+) diff --git a/content/docs/next-release/operator.md b/content/docs/next-release/operator.md index 63ba08d5..adc8bf22 100644 --- a/content/docs/next-release/operator.md +++ b/content/docs/next-release/operator.md @@ -660,6 +660,18 @@ simplest-query * 192.168.122.34 80 3m In this example, the Jaeger UI is available at http://192.168.122.34. +To enable TLS in the Ingress, pass a `secretName` with the name of a [Secret](https://kubernetes.io/docs/concepts/configuration/secret/) containing the TLS certificate: + +```yaml +apiVersion: jaegertracing.io/v1 +kind: Jaeger +metadata: + name: ingress-with-tls +spec: + ingress: + secretName: my-tls-secret +``` + ## OpenShift When the Operator is running on OpenShift, the Operator will automatically create a `Route` object for the query services. Use the following command to check the hostname/port: