homelab: v0.3.1 — fix k8s db PG target (resolve CNPG primary pod, not the Service)
`k8s db <app>` (Postgres path) execed `pg-cluster-rw`, which is the CNPG read-write SERVICE, not a pod — so kubectl exec failed with `pods "pg-cluster-rw" not found`. The unit test only checked the plan; the verb was never fired at live state (the gap flagged in v0.2), so it shipped broken. Fix: the PG plan now carries a label selector (cnpg.io/instanceRole=primary) instead of a pod name, and k8s db resolves the actual primary POD via `kubectl get pod -l <selector>` before exec. MySQL path (real pod mysql-standalone-0) unchanged. Live-verified both paths (psql + mysql). Co-Authored-By: Claude Opus 4.8 <noreply@anthropic.com>
This commit is contained in:
parent
90c944a265
commit
787ce4edfa
4 changed files with 25 additions and 6 deletions
|
|
@ -1 +1 @@
|
|||
v0.3.0
|
||||
v0.3.1
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue