From 2cb9515a571d8cdd36fd4fedbde8e98f3e72e76f Mon Sep 17 00:00:00 2001 From: Bram Schuur Date: Fri, 27 Dec 2024 14:35:58 +0100 Subject: [PATCH 1/2] STAC-0: Add warning for enabling TLS --- setup/install-stackstate/kubernetes_openshift/ingress.md | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/setup/install-stackstate/kubernetes_openshift/ingress.md b/setup/install-stackstate/kubernetes_openshift/ingress.md index dab5c630c..18c65d41c 100644 --- a/setup/install-stackstate/kubernetes_openshift/ingress.md +++ b/setup/install-stackstate/kubernetes_openshift/ingress.md @@ -16,6 +16,10 @@ The SUSE Observability Helm chart exposes an `ingress` section in its values. Th To configure the ingress for SUSE Observability, create a file `ingress_values.yaml` with contents like below. Replace `MY_DOMAIN` with your own domain \(that's linked with your ingress controller\) and set the correct name for the `tls-secret`. Consult the documentation of your ingress controller for the correct annotations to set. All fields below are optional, for example, if no TLS will be used, omit that section but be aware that SUSE Observability also doesn't encrypt the traffic. +{% hint style="warning" %} +Not that setting up TLS is required for the use of the rancher UI extension. +{% endhint %} + ```text ingress: enabled: true From 14b24452135c9da7a7672d52ee131fb53808483c Mon Sep 17 00:00:00 2001 From: Bram Schuur Date: Fri, 27 Dec 2024 15:07:41 +0100 Subject: [PATCH 2/2] STAC-0: Fix typo --- setup/install-stackstate/kubernetes_openshift/ingress.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/setup/install-stackstate/kubernetes_openshift/ingress.md b/setup/install-stackstate/kubernetes_openshift/ingress.md index 18c65d41c..458594f04 100644 --- a/setup/install-stackstate/kubernetes_openshift/ingress.md +++ b/setup/install-stackstate/kubernetes_openshift/ingress.md @@ -17,7 +17,7 @@ The SUSE Observability Helm chart exposes an `ingress` section in its values. Th To configure the ingress for SUSE Observability, create a file `ingress_values.yaml` with contents like below. Replace `MY_DOMAIN` with your own domain \(that's linked with your ingress controller\) and set the correct name for the `tls-secret`. Consult the documentation of your ingress controller for the correct annotations to set. All fields below are optional, for example, if no TLS will be used, omit that section but be aware that SUSE Observability also doesn't encrypt the traffic. {% hint style="warning" %} -Not that setting up TLS is required for the use of the rancher UI extension. +Note that setting up TLS is required for the use of the rancher UI extension. {% endhint %} ```text