Description
What would you like added?
I would like the status of Runner Pods to be reported as Healthy in ArgoCD when they are successfully connected to GitHub and operational as self-hosted runners.
Currently, even after a runner pod is fully functional — connected to GitHub and capable of processing workflows — ArgoCD continues to show its status as Progressing. This behavior makes it difficult for users to rely on ArgoCD's UI to determine whether runners are ready.
If this is not the intended behavior, I would like to propose a fix that makes the health check compatible with ArgoCD, so that the correct status is reflected in the UI.
Why is this needed?
While the runner functionality itself is not impaired, ArgoCD is one of the most widely used GitOps tools in Kubernetes environments. Many users rely on ArgoCD’s health status to monitor application states through its GUI.
Incorrectly showing runner pods as Progressing — even when they are operating correctly — can lead to confusion, false alerts, or unnecessary debugging. Ensuring compatibility with ArgoCD will significantly improve user experience and clarity in GitOps workflows.
We understand that the core runner controller logic may not explicitly support ArgoCD, but if there is no deliberate design decision behind this behavior, improving the health status reporting would be beneficial for many teams.
Additional context
I have already implemented a patch that modifies the pod status evaluation so ArgoCD correctly interprets the runner pods as Healthy once they are ready.
If the maintainers agree that this is a reasonable enhancement, I would be happy to submit a pull request for review.
Let me know if this behavior is intentional or if there is a recommended approach for aligning with ArgoCD health checks.