grafana: drop alerting Service and POD_IP env owned by grafana-operator #510
Reference in New Issue
Block a user
Delete Branch "benvin/grafana-alerting-dedupe"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
grafana-operator already creates the headless
grafana-alertingService (port 9094) and injectsPOD_IPinto the grafana container, so the copies added in #509 make Argo CD and the operator fight over the same objects.service-alerting.yamlfrom the grafana basePOD_IPenv entry from the Grafana CRunified_alertingha_*config, which targets the operator's Servicegrafana-alertingService sets nopublishNotReadyAddresses(the removed one did), soha_peersDNS lists only Ready pods; on a cold 3-replica start peers are found only after readiness (gossip retries, converges). Accept, or confirm HA forms after rollout.