docs: monitoring — URLs Prometheus et AlertManager accessibles via Ingress

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>
This commit is contained in:
alkatrazz 2026-05-13 22:31:46 +02:00
parent e0d233da02
commit 0cd45b7be9

View file

@ -10,19 +10,13 @@ Chart : `kube-prometheus-stack` v85.0.2 (Prometheus Operator).
| Service | URL | Login | Mot de passe |
|---|---|---|---|
| **Grafana** | http://grafana.lab.local | `admin` | `funk-grafana` |
| **AlertManager** | http://alertmanager.lab.local ¹ | — | — |
| **Prometheus** | http://prometheus.lab.local ¹ | — | — |
¹ Ingress non encore créés — accessible via port-forward :
```bash
kubectl port-forward svc/kube-prometheus-stack-prometheus -n monitoring 9090:9090
kubectl port-forward svc/kube-prometheus-stack-alertmanager -n monitoring 9093:9093
```
| **AlertManager** | http://alertmanager.lab.local | — | — |
| **Prometheus** | http://prometheus.lab.local | — | — |
> DNS `*.lab.local` ne résout que depuis le cluster LAN (192.168.10.0/24).
> Depuis le poste perso (192.168.1.x), les entrées sont dans `/etc/hosts` :
> ```
> 192.168.10.200 grafana.lab.local argocd.lab.local
> 192.168.10.200 grafana.lab.local argocd.lab.local prometheus.lab.local alertmanager.lab.local
> ```
---