<#6559 [charts] Flyte-Binary: Add preInitContainer...
# flyte-github
c
#6559 [charts] Flyte-Binary: Add preInitContainers value Pull request opened by hylje ## Tracking issue There does not seem to be existing Github issues for this. ## Why are the changes needed?
deployment.initContainers
are inserted after the
wait-for-db
init container, making it wait forever if the database connection is also provided by an init container. ## What changes were proposed in this pull request? Adds
deployment.preInitContainers
value that inserts its contents before any other init container in the deployment. Example values configuration snippet for cloud-sql-proxy:
Copy code
deployment:
  (...)
  preInitContainers:
    - name: cloud-sql-proxy
      restartPolicy: Always
      image: gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.14.1
      args:
        - "--private-ip"
        - "--auto-iam-authn"
        - "--structured-logs"
        - "--port=5433"
        - "<Cloud SQL connection name>"
## How was this patch tested? Deployed the chart including the new value and ran a test execution with the deployed chart. ### Labels • added: New
deployment.preInitContainers
value for
flyte-binary
Helm chart ### Setup process ### Screenshots ## Check all the applicable boxes • I updated the documentation accordingly. • All new and existing tests passed. • All commits are signed-off. ## Docs link No new docs, beside the Helm-docs generated README for the new value. https://bito.ai#summarystart| ### Summary by Bito This pull request adds a new configuration option, preInitContainers, to the Flyte-Binary Helm chart, enabling users to specify additional init containers. This enhancement aims to prevent deployment hangs related to database connection issues by modifying the deployment template and values configuration file. flyteorg/flyte