[stable/2023.1] fix: use openstack_helm_ingress_secret_name when set for monitoring (#1406)
This is an automated cherry-pick of #1386
/assign mnaser
diff --git a/roles/kube_prometheus_stack/vars/main.yml b/roles/kube_prometheus_stack/vars/main.yml
index 4cf2386..b32069a 100644
--- a/roles/kube_prometheus_stack/vars/main.yml
+++ b/roles/kube_prometheus_stack/vars/main.yml
@@ -80,7 +80,7 @@
hosts:
- "{{ kube_prometheus_stack_alertmanager_host }}"
tls:
- - secretName: alertmanager-tls
+ - secretName: "{{ openstack_helm_ingress_secret_name | default('alertmanager-tls')}}"
hosts:
- "{{ kube_prometheus_stack_alertmanager_host }}"
alertmanagerSpec:
@@ -186,7 +186,7 @@
hosts:
- "{{ kube_prometheus_stack_grafana_host }}"
tls:
- - secretName: grafana-tls
+ - secretName: "{{ openstack_helm_ingress_secret_name | default('grafana-tls')}}"
hosts:
- "{{ kube_prometheus_stack_grafana_host }}"
sidecar:
@@ -305,7 +305,7 @@
hosts:
- "{{ kube_prometheus_stack_prometheus_host }}"
tls:
- - secretName: prometheus-tls
+ - secretName: "{{ openstack_helm_ingress_secret_name | default('prometheus-tls')}}"
hosts:
- "{{ kube_prometheus_stack_prometheus_host }}"
prometheusSpec: