Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix ProxyKube not reporting its readiness #12150

Merged
merged 1 commit into from
Apr 21, 2022

Conversation

espadolini
Copy link
Contributor

After #11249 the /readyz diag endpoint will only report OK if enough components have heartbeated without error; however, the proxy.kube service will not actually heartbeat unless it's running in "legacy" mode, also acting as a kubernetes_service. This PR makes it so that if that's the case, an initial OK heartbeat is reported for that component (similarly to what a db_service will do when running in dynamic mode with no configured databases).

Fixes #12139.

@espadolini espadolini merged commit 6cdcfe7 into master Apr 21, 2022
@espadolini espadolini deleted the espadolini/proxykube-heartbeat branch April 21, 2022 15:32
r0mant added a commit that referenced this pull request Apr 26, 2022
r0mant added a commit that referenced this pull request Apr 26, 2022
* Revert "Make `PortList.Pop()` thread-safe (#11799)"

This reverts commit a17337d.

* Revert "Ensure stateOK is reported only when all components have sent updates (#11249)"

This reverts commit b749302.

* Revert "Throw startup error if `TeleportReadyEvent` is not emitted (#11725)"

This reverts commit 933e247.

* Revert "Fix ProxyKube not reporting its readiness (#12150)"

This reverts commit 6cdcfe7.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Teleport 9.1.0 Pod never enters Ready state
4 participants