chrisfu cf51335ced Fix kube context handling and monitoring eligibility ... - detect local k3s node kubeconfig and skip kubectx/use-context mutation when already targeting local API\n- add configurable KUBE_CONTEXT_NAME resolution with compatibility fallbacks and switch only when required\n- update init scripts to use ensure_kube_context helper naming\n- broaden monitoring eligibility to discovered /synology/d### mounts so /synology/d004 qualifies\n- add focused kube-context and topology tests covering local/remote and read-only kubeconfig cases Co-authored-by: Junie <junie@jetbrains.com>		2026-03-23 13:50:29 -07:00
..
cnpg-placement	Separate k3s and k3d config defaults; normalize k3s image registry refs	2026-03-23 03:48:58 -07:00
dev	checkpoint: tighten CNPG k3s storage flow and policy updates	2026-03-23 12:39:03 -07:00
postgresql	Refactor to support mode-scoped DB build contexts and versioning	2026-03-22 05:47:50 -07:00
prod	Rename prole-db to knoe-db, add knoe-auth as cluster-internal KDC	2026-03-22 22:16:21 -07:00
service	Fix kube context handling and monitoring eligibility	2026-03-23 13:50:29 -07:00
test	Rename prole-db to knoe-db, add knoe-auth as cluster-internal KDC	2026-03-22 22:16:21 -07:00
database_versions.json	Rename Prole storage objects to Synology and sync deployment updates	2026-03-22 21:50:02 -07:00
port-mapping.cfg	checkpoint: tighten CNPG k3s storage flow and policy updates	2026-03-23 12:39:03 -07:00