Change service type to ClusterIP for Prometheus, Grafana, and Alertmanager; add Ingress configuration for monitoring services

Author: karimzakzouk

argocd/monitoring.yml

@@ -16,16 +16,16 @@ spec:
           enabled: true  # Enable CRD installation
         prometheus:
           service:
-            type: LoadBalancer
+            type: ClusterIP
         grafana:
           service:
-            type: LoadBalancer
+            type: ClusterIP
           admin:
             existingSecret: grafana-admin-secret
             passwordKey: admin-password
         alertmanager:
           service:
-            type: LoadBalancer
+            type: ClusterIP
   destination:
     server: https://kubernetes.default.svc
     namespace: ${MONITORING_NAMESPACE}
@@ -36,4 +36,37 @@ spec:
     syncOptions:
       - CreateNamespace=true
       - ServerSideApply=true
-      - SkipDryRunOnMissingResource=true
+      - SkipDryRunOnMissingResource=true
+
+---
+apiVersion: networking.k8s.io/v1
+kind: Ingress
+metadata:
+  name: monitoring-ingress
+  namespace: ${MONITORING_NAMESPACE}
+spec:
+  rules:
+  - host: monitoring.yourdomain.com
+    http:
+      paths:
+      - path: /grafana
+        pathType: Prefix
+        backend:
+          service:
+            name: kube-prometheus-stack-grafana
+            port:
+              number: 80
+      - path: /prometheus
+        pathType: Prefix
+        backend:
+          service:
+            name: kube-prometheus-stack-prometheus
+            port:
+              number: 9090
+      - path: /alertmanager
+        pathType: Prefix
+        backend:
+          service:
+            name: kube-prometheus-stack-alertmanager
+            port:
+              number: 9093