Ingress Monitor Controller

Ingress Monitor Controller keeps external uptime checks aligned with the application endpoints declared in Kubernetes. When a monitored Ingress or route changes, it can update the corresponding check at a supported monitoring provider instead of requiring a manual edit. It is useful for preventing newly published services from being missed by availability monitoring. It configures the checks; another ingress controller serves the traffic, and the monitoring provider performs the probes.

Current guidance

The historical stable chart identifies Stakater’s Ingress Monitor Controller. The current upstream describes an operator using EndpointMonitor resources to reconcile Kubernetes Ingress or OpenShift Route endpoints with supported uptime-checking providers. This is monitoring configuration automation, separate from the controller that serves application traffic.

Choose the provider and its credentials explicitly, then review which namespaces and endpoints the controller may publish to that external service. Internal hostnames or authenticated health URLs may need a different monitoring approach. Check that a successful endpoint response represents useful application health rather than merely a proxy’s default page.

The repository documents creationDelay for DNS readiness, resyncPeriod and enableMonitorDeletion. Decide whether deleting an Ingress should remove its external monitor, and test create, rename and deletion behavior with a disposable monitor first. Preserve alert ownership and naming during migration so existing incidents are not silently detached. The archived stable chart should be evaluated independently of the current operator instructions, and each provider integration needs its own verification; the README even qualifies the testing status of some integrations.