Repository navigation
[Feature]: Improvement: Modify quadlets to be marked as ready only after passing a HealthCheck #68
Description
Describe the feature
Each of the current quadlets has little or no configuration of the quadlet HealthCheck property. Adding this in would increase deployment robustness.
Why do you want this feature?
Podman quadlets come with a HealthCheck feature out of the box which can be wired into systemd's dependency notifier. More explicitly, it can be used to prevent signaling readiness too early to dependent service units downstream.
The current configuration does start all quadlet services in dependency order, but does not ensure any service is fully functional before launching the services which depend on it.
Alternatives you've considered
NA
Additional context
No response
Code of Conduct
- I agree to follow this project's Code of Conduct
Metadata
Metadata
Assignees
Labels
No labels
Activity
synackd commentedon Aug 7, 2026
Great idea! Can I assign this to you, @seantronsen?
seantronsen commentedon Aug 8, 2026
Sure, I can do it after #64
seantronsen commentedon Aug 10, 2026
@synackd IIRC, the chainguard containers are pretty barebones (no tools like curl or dig) which negatively impacts the ability to set up HealthCmd since it runs inside the container.
Any ideas? Or should we kill this and keep chainguard?
synackd commentedon Aug 10, 2026
We can keep ChainGuard and minimally add whichever tools we need, I think.
seantronsen commentedon Aug 10, 2026
What's the policy for CVEs here? For example, we'll need 'curl' for most of the testing and curl is a frequent CVE source.