A. F. Dudley 967936e524 Multi-deployment: one k8s Deployment per pod in stack.yml ... Each pod entry in stack.yml now creates its own k8s Deployment with independent lifecycle and update strategy. Pods with PVCs get Recreate, pods without get RollingUpdate. This enables maintenance services that survive main pod restarts. - cluster_info: get_deployments() builds per-pod Deployments, Services - cluster_info: Ingress routes to correct per-pod Service - deploy_k8s: _create_deployment() iterates all Deployments/Services - deployment: restart swaps Ingress to maintenance service during Recreate - spec: add maintenance-service key Single-pod stacks are backward compatible (same resource names). Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>		2026-03-20 01:40:45 +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	Multi-deployment: one k8s Deployment per pod in stack.yml	2026-03-20 01:40:45 +00:00
deploy_k8s.py	Multi-deployment: one k8s Deployment per pod in stack.yml	2026-03-20 01:40:45 +00:00
helpers.py	so-m3m: add credentials-files spec key for on-disk credential injection	2026-03-18 21:55:28 +00:00
k8s_command.py	Apply pre-commit linting fixes	2026-01-21 20:58:31 -05:00