feat(helm): add configurable initContainers (startup containers) to Collab deployment

Fixes: #203

- This PR adds support for configurable “startup containers” by allowing users to define Kubernetes initContainers in the Collab Helm chart.

Author: danc094codetogether

charts/collab/templates/deployment.yaml

@@ -29,6 +29,12 @@ spec:
         - name: {{ include "codetogether.fullname" . }}-pull-secret
       {{- end }}
       serviceAccountName: {{ include "codetogether.serviceAccountName" . }}
+
+      {{- with .Values.initContainers }}
+      initContainers:
+        {{- toYaml . | nindent 8 }}
+      {{- end }}
+      
       containers:
         - name: {{ .Chart.Name }}
           securityContext:

charts/collab/values.yaml

@@ -212,6 +212,19 @@ serviceAccount:
 
 podAnnotations: {}
 
+# Optional: add initContainers (startup containers) to the pod spec.
+# Useful to wait for dependencies (e.g., Intel URL reachability, locator DB readiness, etc.)
+# before CodeTogether Collab starts.
+initContainers: []
+# Example:
+# initContainers:
+#   - name: wait-for-intel
+#     image: busybox:1.36
+#     command: ["sh", "-c"]
+#     args:
+#       - >
+#         until nc -z your-intel-host 443; do echo "Waiting for Intel..."; sleep 2; done
+
 securityContext: {} #defaults
   # capabilities:
   #   drop: