fix: provisioner no longer hosts service (#4279)

- No need for readiness checks on provisioner. - No need for provisioner-service.yaml now that there is no service - Rename cron file for consistency
block · Feb 4, 2025 · 2c13a03 · 2c13a03
1 parent 4e0fd88
commit 2c13a03
Show file tree

Hide file tree

Showing 3 changed files with 0 additions and 37 deletions.
diff --git a/charts/ftl/templates/cron-deployment.yaml → charts/ftl/templates/cron.yaml b/charts/ftl/templates/cron-deployment.yaml → charts/ftl/templates/cron.yaml
diff --git a/charts/ftl/templates/provisioner-services.yaml b/charts/ftl/templates/provisioner-services.yaml
diff --git a/charts/ftl/templates/provisioner.yaml b/charts/ftl/templates/provisioner.yaml
@@ -47,19 +47,6 @@ spec:
               containerPort: {{ .containerPort }}
               protocol: {{ .protocol | default "TCP" }}
             {{- end }}
-          readinessProbe:
-            {{- if .Values.provisioner.readinessProbe }}
-            {{- toYaml .Values.provisioner.readinessProbe | nindent 12 }}
-            {{- else }}
-            httpGet:
-              path: /healthz
-              port: {{ (index .Values.provisioner.ports 0).containerPort }}
-            initialDelaySeconds: 1
-            periodSeconds: 2
-            timeoutSeconds: 2
-            successThreshold: 1
-            failureThreshold: 15
-            {{- end }}
           volumeMounts:
             - mountPath: /config
               name: config