Default Liveness and Readiness endpoints return 404

[David Pell]

I found this earlier issue but it's closed. Given the existence of default liveness and readiness endpoints that are URL paths, it'd be nice if ping-style healthchecks were added by default. It takes some digging to see that, despite the existence of default HTTP endpoints that get registered in the manager options by default, you need to add handlers manually or use a TCP check.

[Kubernetes Triage Robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues.

This bot triages un-triaged issues according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale