Consider adding liveness/readiness probes and metrics endpoint to test extension #7258
Labels
area/clusterclass
Issues or PRs related to clusterclass
kind/feature
Categorizes issue or PR as related to a new feature.
lifecycle/frozen
Indicates that an issue or PR should not be auto-closed due to staleness.
triage/accepted
Indicates an issue or PR is ready to be actively worked on.
To make our test extension / the reference implementation more production ready it would be great if we have readiness/liveness and metrics endpoints.
Details
I think we have at least two options:
It would be great if we could also use the webhookServer.StartedChecker for our liveness/readiness endpoints like we do in our controllers here:
cluster-api/main.go
Lines 284 to 292 in 73f436e
P.S. tilt-prepare already modifies our test extension deployment as if it would have a metrics endpoint (it adds the metrics port)
/area topology
/kind feature
The text was updated successfully, but these errors were encountered: