feat(plane-enterprise): make live init container image configurable

charts/plane-enterprise/Chart.yaml

@@ -5,7 +5,7 @@ description: Meet Plane. An Enterprise software development tool to manage issue
 
 type: application
 
-version: 3.5.2
+version: 3.5.3
 appVersion: "3.1.2"
 
 home: https://plane.so/

charts/plane-enterprise/README.md

@@ -727,6 +727,7 @@ the bundled datastores off. Three things to know before you use it:
 | services.live.memoryRequest        |                    512Mi                     |          | Every deployment in kubernetes can be set to use minimum memory they are allowed to use. This key sets the memory request for this deployment to use.                                                           |
 | services.live.cpuRequest           |                     100m                     |          | Every deployment in kubernetes can be set to use minimum cpu they are allowed to use. This key sets the cpu request for this deployment to use.                                                                 |
 | services.live.image                | makeplane/live-commercial |          | This deployment needs a preconfigured docker image to function. Docker image name is provided by the owner and must not be changed for this deployment                                                          |
+| services.live.init_image           |                   busybox                    |          | Using this key, user can provide the docker image used by the `live` init container, which assembles the custom S3 CA bundle. Only rendered when a custom S3 CA is configured (`airgapped.enabled` with an S3 CA secret). An override must be BusyBox-compatible: the init script needs `/bin/sh`, `ls`, `cat`, and `touch`. If any is missing the init container fails and `live` never starts |
 | services.live.pullPolicy           |                    Always                    |          | Using this key, user can set the pull policy for the deployment of `live`.                                                                                                                                      |
 | env.live_sentry_dsn                |                                              |          | (optional) Live service deployment comes with some of the preconfigured integration. Sentry is one among those. Here user can set the Sentry provided DSN for this integration.                                 |
 | env.live_sentry_environment        |                                              |          | (optional) Live service deployment comes with some of the preconfigured integration. Sentry is one among those. Here user can set the Sentry environment name (as configured in Sentry) for this integration.   |

charts/plane-enterprise/questions.yml

@@ -51,6 +51,10 @@ questions:
     type: string
     required: true
     default: "makeplane/live-commercial"
+  - variable: services.live.init_image
+    label: Live Init Docker Image
+    type: string
+    default: "busybox"
   - variable: services.monitor.image
     label: Monitor Docker Image
     type: string

charts/plane-enterprise/templates/workloads/live.deployment.yaml

@@ -50,7 +50,7 @@ spec:
       {{- if include "plane.s3CAEnabled" . }}
       initContainers:
       - name: prepare-ca-bundle
-        image: busybox
+        image: {{ .Values.services.live.init_image | default "busybox" }}
         {{- include "plane.containerSecurityContext" . }}
         command:
           - /bin/sh

charts/plane-enterprise/values.yaml

@@ -383,6 +383,10 @@ services:
     memoryRequest: 512Mi
     cpuRequest: 100m
     image: makeplane/live-commercial
+    # Image for the prepare-ca-bundle init container (rendered only when a custom
+    # S3 CA is configured). Must be BusyBox-compatible: the script needs /bin/sh,
+    # ls, cat and touch.
+    init_image: busybox
     pullPolicy: Always
     assign_cluster_ip: false
     nodeSelector: {}