🚚(helm) specify unique component names for all backend jobs
Update backend job configurations to use distinct component names instead of sharing names with deployments. Prevents conflicts during cluster updates and migrations that were causing unexpected behavior. Improves deployment reliability and resource identification.
This commit is contained in:
committed by
aleb_the_flash
parent
0206762e6d
commit
d2da1e37b9
@@ -1,6 +1,6 @@
|
||||
{{- $envVars := include "meet.common.env" (list . .Values.backend) -}}
|
||||
{{- $fullName := include "meet.backend.fullname" . -}}
|
||||
{{- $component := "backend" -}}
|
||||
{{- $component := "backend-createsuperuser" -}}
|
||||
apiVersion: batch/v1
|
||||
kind: Job
|
||||
metadata:
|
||||
|
||||
@@ -1,6 +1,6 @@
|
||||
{{- $envVars := include "meet.common.env" (list . .Values.backend) -}}
|
||||
{{- $fullName := include "meet.backend.fullname" . -}}
|
||||
{{- $component := "backend" -}}
|
||||
{{- $component := "backend-migrate" -}}
|
||||
apiVersion: batch/v1
|
||||
kind: Job
|
||||
metadata:
|
||||
|
||||
Reference in New Issue
Block a user