MOSIP-28488 (#496)

* [MOSIP-28488] Updated backoffLimit in job.yaml Signed-off-by: Mohan E <[email protected]> * [MOSIP-28488] Updated backoffLimit in values.yaml Signed-off-by: Mohan E <[email protected]> * Update values.yaml Signed-off-by: Mohan E <[email protected]> * [MOSIP-28488] Updated backoffLimit. * [MOSIP-28488] Updated backoffLimit. * [MOSIP-28488] Updated cronjob.yaml * [MOSIP-28488] Updated jobs.yaml Signed-off-by: Mohan E <[email protected]> --------- Signed-off-by: Mohan E <[email protected]>
mosip · Jul 21, 2023 · c0d3801 · c0d3801
1 parent 138bc91
commit c0d3801
Show file tree

Hide file tree

Showing 41 changed files with 76 additions and 4 deletions.
diff --git a/charts/apitestrig/templates/cronjob.yaml b/charts/apitestrig/templates/cronjob.yaml
@@ -15,7 +15,7 @@ spec:
   schedule: {{ $.Values.crontime }}
   jobTemplate:
     spec:
-      backoffLimit: 2 # this has very low chance of failing, as all this does
+      backoffLimit: {{ $.Values.backoffLimit }} # this has very low chance of failing, as all this does
                       # is prompt kubernetes to schedule new replica set for
       # the deployment
       # activeDeadlineSeconds: 600 # timeout, makes most sense with

diff --git a/charts/apitestrig/values.yaml b/charts/apitestrig/values.yaml
@@ -194,6 +194,10 @@ customLivenessProbe: {}
 ##
 customReadinessProbe: {}
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 ## Update strategy - only really applicable for deployments with RWO PVs attached
 ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
 ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will

diff --git a/charts/dslorchestrator/templates/cronjob.yaml b/charts/dslorchestrator/templates/cronjob.yaml
@@ -13,7 +13,7 @@ spec:
   schedule: {{ .Values.crontime }}
   jobTemplate:
     spec:
-      backoffLimit: 2 # this has very low chance of failing, as all this does
+      backoffLimit: {{ $.Values.backoffLimit }} # this has very low chance of failing, as all this does
                       # is prompt kubernetes to schedule new replica set for
       # the deployment
       # activeDeadlineSeconds: 600 # timeout, makes most sense with

diff --git a/charts/dslorchestrator/values.yaml b/charts/dslorchestrator/values.yaml
@@ -194,6 +194,10 @@ customLivenessProbe: {}
 ##
 customReadinessProbe: {}
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 ## Update strategy - only really applicable for deployments with RWO PVs attached
 ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
 ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will

diff --git a/charts/idrepo-saltgen/templates/job.yaml b/charts/idrepo-saltgen/templates/job.yaml
@@ -13,6 +13,7 @@ metadata:
     {{- end }}
 
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels: {{- include "common.labels.standard" . | nindent 8 }}

diff --git a/charts/idrepo-saltgen/values.yaml b/charts/idrepo-saltgen/values.yaml
@@ -166,6 +166,10 @@ customLivenessProbe: {}
 ##
 customReadinessProbe: {}
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 ## Update strategy - only really applicable for deployments with RWO PVs attached
 ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
 ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will

diff --git a/charts/keycloak-init/templates/job.yaml b/charts/keycloak-init/templates/job.yaml
@@ -5,6 +5,7 @@ metadata:
   labels:
     {{- include "keycloak-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/keycloak-init/values.yaml b/charts/keycloak-init/values.yaml
@@ -65,6 +65,10 @@ resources: {}
   #   cpu: 100m
   #   memory: 128Mi
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 nodeSelector: {}
 
 tolerations: []

diff --git a/charts/keygen/templates/job.yaml b/charts/keygen/templates/job.yaml
@@ -13,6 +13,7 @@ metadata:
     {{- end }}
 
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels: {{- include "common.labels.standard" . | nindent 8 }}

diff --git a/charts/keygen/values.yaml b/charts/keygen/values.yaml
@@ -166,6 +166,10 @@ customLivenessProbe: {}
 ##
 customReadinessProbe: {}
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 ## Update strategy - only really applicable for deployments with RWO PVs attached
 ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
 ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will

diff --git a/charts/masterdata-loader/templates/job.yaml b/charts/masterdata-loader/templates/job.yaml
@@ -5,6 +5,7 @@ metadata:
   labels:
     {{- include "masterdata-loader.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/masterdata-loader/values.yaml b/charts/masterdata-loader/values.yaml
@@ -65,6 +65,10 @@ resources: {}
   #   cpu: 100m
   #   memory: 128Mi
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 nodeSelector: {}
 
 tolerations: []

diff --git a/charts/partner-onboarder/templates/jobs.yaml b/charts/partner-onboarder/templates/jobs.yaml
@@ -14,6 +14,7 @@ metadata:
     {{- include "common.tplvalues.render" ( dict "value" $.Values.commonAnnotations "context" $ ) | nindent 4 }}
     {{- end }}
 spec:
+  backoffLimit: {{ $.Values.backoffLimit }}
   template:
     metadata:
       labels: {{- include "common.labels.standard" $ | nindent 10 }}
@@ -63,4 +64,4 @@ spec:
               {{- end }}
               {{- end }}
 {{- end }}
-{{- end }}
+{{- end }}
diff --git a/charts/partner-onboarder/values.yaml b/charts/partner-onboarder/values.yaml
@@ -232,6 +232,10 @@ customLivenessProbe: {}
 ##
 customReadinessProbe: {}
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 ## Update strategy - only really applicable for deployments with RWO PVs attached
 ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
 ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will

diff --git a/charts/postgres-init/templates/audit-job.yaml b/charts/postgres-init/templates/audit-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/authdevice-job.yaml b/charts/postgres-init/templates/authdevice-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/credential-job.yaml b/charts/postgres-init/templates/credential-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/digitalcard-job.yaml b/charts/postgres-init/templates/digitalcard-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/esignet-job.yaml b/charts/postgres-init/templates/esignet-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/hotlist-job.yaml b/charts/postgres-init/templates/hotlist-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/ida-job.yaml b/charts/postgres-init/templates/ida-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/idmap-job.yaml b/charts/postgres-init/templates/idmap-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/idrepo-job.yaml b/charts/postgres-init/templates/idrepo-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/kernel-job.yaml b/charts/postgres-init/templates/kernel-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/keymgr-job.yaml b/charts/postgres-init/templates/keymgr-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/master-job.yaml b/charts/postgres-init/templates/master-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/mockidentitysystem-job.yaml b/charts/postgres-init/templates/mockidentitysystem-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/pms-job.yaml b/charts/postgres-init/templates/pms-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/prereg-job.yaml b/charts/postgres-init/templates/prereg-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/regdevice-job.yaml b/charts/postgres-init/templates/regdevice-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/regprc-job.yaml b/charts/postgres-init/templates/regprc-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/resident-job.yaml b/charts/postgres-init/templates/resident-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     {{- include "postgres-init.labels" . | nindent 4 }}
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/postgres-init/templates/toolkit-job.yaml b/charts/postgres-init/templates/toolkit-job.yaml
@@ -14,6 +14,8 @@ metadata:
 
 spec:
 
+  backoffLimit: {{ .Values.backoffLimit }}
+
   template:
 
     metadata:

diff --git a/charts/postgres-init/values.yaml b/charts/postgres-init/values.yaml
@@ -65,6 +65,10 @@ resources: {}
   #   cpu: 100m
   #   memory: 128Mi
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 nodeSelector: {}
 
 tolerations: []

diff --git a/charts/regproc-salt/templates/job.yaml b/charts/regproc-salt/templates/job.yaml
@@ -13,6 +13,7 @@ metadata:
     {{- end }}
 
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels: {{- include "common.labels.standard" . | nindent 8 }}

diff --git a/charts/regproc-salt/values.yaml b/charts/regproc-salt/values.yaml
@@ -166,6 +166,10 @@ customLivenessProbe: {}
 ##
 customReadinessProbe: {}
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 ## Update strategy - only really applicable for deployments with RWO PVs attached
 ## If replicas = 1, an update can get "stuck", as the previous pod remains attached to the
 ## PV, and the "incoming" pod can never start. Changing the strategy to "Recreate" will

diff --git a/charts/reporting-init/templates/debezium-job.yaml b/charts/reporting-init/templates/debezium-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     app.kubernetes.io/name: {{ .Release.Name }}-debezium-job
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/reporting-init/templates/es-kafka-connect-job.yaml b/charts/reporting-init/templates/es-kafka-connect-job.yaml
@@ -6,6 +6,7 @@ metadata:
   labels:
     app.kubernetes.io/name: {{ .Release.Name }}-es-kafka-conn-job
 spec:
+  backoffLimit: {{ .Values.backoffLimit }}
   template:
     metadata:
       labels:

diff --git a/charts/reporting-init/values.yaml b/charts/reporting-init/values.yaml
@@ -41,3 +41,7 @@ es_kafka_connectors:
   delay_between_connectors: "0s"
 
 kibana_enabled: {}
+
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
diff --git a/charts/restart-cron/templates/cronjob.yaml b/charts/restart-cron/templates/cronjob.yaml
@@ -7,7 +7,7 @@ spec:
   schedule: {{ .Values.schedule.crontime }}
   jobTemplate:
     spec:
-      backoffLimit: 2
+      backoffLimit: {{ .Values.backoffLimit }}
       activeDeadlineSeconds: 600
       template:
           spec:

diff --git a/charts/restart-cron/values.yaml b/charts/restart-cron/values.yaml
@@ -16,6 +16,10 @@ namespaces:
 schedule:
   crontime: "0 3 * * *"   ## run cronjob every day at 3 AM (time hr: 0-23 )
 
+## "backoff" strategy - It is used when dealing with resources that are retrying or recovering from failures.
+##
+backoffLimit: 0
+
 serviceAccount:
   create: true
   name: pod-deleter