No PodDisruptionBudget for the Hatchet engine or the bundled PostgreSQL

[raisedadead]

Summary

Only the deploy-proxy Deployment has a PodDisruptionBudget. Neither the Hatchet engine nor the bundled PostgreSQL has one.

The artemis PDB deliberately scopes its selector to app.kubernetes.io/component: deploy-proxy — correctly, since a bare selector would also match the Postgres and backup pods. The side effect is that those workloads are left with no budget at all, and both are single-replica.

Fix direction

• Add a PDB for the Hatchet engine in the hatchet chart (k3s/gxy-management/apps/hatchet/charts/hatchet/ — no pdb.yaml exists there today).
• Add a component-scoped PDB for the Postgres StatefulSet in the artemis chart.
• For single-replica workloads a PDB cannot prevent disruption outright, but it makes drains explicit rather than silent, and documents the intent.