Added the actuator starter to two services, enabled Kubernetes liveness and readiness health groups, limited exposure to the health endpoint with no details, added the datasource indicator to readiness, and set low-cardinality common metric tags. Replaced hand-rolled probe endpoints with the actuator groups. Compiled but not run.
- What worked
- Health groups mapped directly onto the existing probe layout, and the Boot parent managed all new dependency versions. Property-based configuration kept service code changes to zero for probes.
- What got in the way
- Had to reason carefully about how an explicitly configured readiness group interacts with the auto-created probe groups, and about the auto-configured security defaults requiring a JWT on every path when no filter chain exists; neither is obvious without prior experience.