edit ingress definitions for alertmanager

sassoftware · Mar 6, 2024 · 0d5c353 · 0d5c353
1 parent 42be8bf
commit 0d5c353
Show file tree

Hide file tree

Showing 3 changed files with 14 additions and 9 deletions.
diff --git a/requirements.yaml b/requirements.yaml
diff --git a/roles/monitoring/templates/host-based/user-values-prom-operator.yaml b/roles/monitoring/templates/host-based/user-values-prom-operator.yaml
@@ -17,6 +17,12 @@ prometheus:
     - {{ V4M_PROMETHEUS_FQDN }}
   prometheusSpec:
     externalUrl: "https://{{ V4M_PROMETHEUS_FQDN }}"
+    alertingEndpoints:
+      - name: v4m-alertmanager
+        port: http-web
+        scheme: https
+        tlsConfig:
+          insecureSkipVerify: true
     storageSpec:
       volumeClaimTemplate:
         spec:

diff --git a/roles/monitoring/templates/path-based/user-values-prom-operator.yaml b/roles/monitoring/templates/path-based/user-values-prom-operator.yaml
@@ -24,7 +24,7 @@ grafana:
 
 # Note that Prometheus and Alertmanager do not have any
 # authentication configured by default, exposing an
-# unauthenticated applicaton without other restrictions
+# unauthenticated application without other restrictions
 # in place is insecure.
 
 prometheus:
@@ -72,3 +72,10 @@ alertmanager:
   alertmanagerSpec:
     routePrefix: /alertmanager
     externalUrl: "https://{{ V4M_BASE_DOMAIN }}/alertmanager"
+    alertingEndpoints:
+      - name: v4m-alertmanager
+        port: http-web
+        pathPrefix: "/alertmanager"
+        scheme: https
+        tlsConfig:
+          insecureSkipVerify: true