stack-orchestrator/stack_orchestrator/deploy/k8s
Prathamesh Musale d65802f8ce fix(k8s): reconcile Caddy image regardless of --skip-cluster-management
The Caddy image reconcile was gated on `not self.skip_cluster_management`
alongside the install path. With --skip-cluster-management being the
default, that meant spec image changes never propagated on normal
restarts — the operator had to pass --perform-cluster-management for
the reconcile to run, which is surprising and conflates cluster
lifecycle ownership with routine workload reconciliation.

Split the two: install still requires cluster-management ownership
(it seeds namespace + secrets + CronJob, which are cluster-creation
concerns). The update-on-reuse patch is a plain k8s-API operation
against a running Deployment — run it in both modes.

Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
2026-04-21 09:02:22 +00:00
..
helm Fix pyright type errors across codebase 2026-01-22 01:10:36 -05:00
__init__.py Rename app -> stack_orchestrator (#625) 2023-11-07 00:06:55 -07:00
cluster_info.py k8s: shared-cluster safety checks and deployment-id decoupling (#748) 2026-04-21 12:17:28 +05:30
deploy_k8s.py fix(k8s): reconcile Caddy image regardless of --skip-cluster-management 2026-04-21 09:02:22 +00:00
helpers.py fix(k8s): template Caddy image by container name, not string match 2026-04-21 08:38:29 +00:00
k8s_command.py Apply pre-commit linting fixes 2026-01-21 20:58:31 -05:00