fix(tenant): add atomic install for etcd HelmRelease
Without atomic: true, Helm install can mark the release as deployed even if some resources (like DataStore) fail to create. This leads to silent failures where etcd StatefulSet is running but DataStore CR is missing, preventing any Kubernetes cluster creation in the tenant. With atomic: true, Helm will fail the install if any resource fails to create, triggering proper retry via install.remediation.retries. Fixes partial resource creation issue described in #2412. Signed-off-by: IvanHunters <xorokhotnikov@gmail.com>
This commit is contained in:
parent
52edffbb9a
commit
6b2425fd25
1 changed files with 1 additions and 0 deletions
|
|
@ -20,6 +20,7 @@ spec:
|
|||
interval: 5m
|
||||
timeout: 30m
|
||||
install:
|
||||
atomic: true
|
||||
remediation:
|
||||
retries: -1
|
||||
upgrade:
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue