Helm Chart V2: airbyte-bootloader volumeMounts gated on singular `extraVolumeMount`, silently dropping mounts
Helm Chart Version
2.2.0 (also present on main as of 2026-09-15)
What step the error happened?
On deploy
Relevant information
airbyte-bootloader/pod.yaml gates its volumeMounts: block on the singular .Values.airbyteBootloader.extraVolumeMount, but renders the plural .Values.airbyteBootloader.extraVolumeMounts inside it.
{{- if .Values.airbyteBootloader.extraVolumeMount }} # <-- singular
volumeMounts:
{{- toYaml .Values.airbyteBootloader.extraVolumeMounts | nindent 8 }} # <-- plural
{{- end }}The volumes: block lower down correctly uses extraVolumes, so setting the documented pair extraVolumes + extraVolumeMounts attaches the volume but silently drops the volumeMount. No error is raised — the pod just starts without the file.
This is the same class of silent-failure bug as #73268, in a different template.
Reproduction
airbyteBootloader:
extraVolumes:
- name: my-ca
configMap:
name: my-ca
extraVolumeMounts:
- name: my-ca
mountPath: /etc/ssl/my-ca
readOnly: truehelm template renders the volume under spec.volumes but produces no volumeMounts entry on the container.
Impact
We hit this enforcing verified TLS (sslmode=verify-full) to an RDS Postgres instance: the bootloader needs the CA bundle mounted to validate the server certificate, and the mount vanishing silently meant certificate verification would fail at startup with no indication that the values were being ignored.
Workaround
Set the singular key to something truthy alongside the real pair:
airbyteBootloader:
extraVolumeMount: true # workaround for the gate typo
extraVolumeMounts: [...]
extraVolumes: [...]Suggested fix
- {{- if .Values.airbyteBootloader.extraVolumeMount }}
+ {{- if .Values.airbyteBootloader.extraVolumeMounts }}Source: airbytehq/airbyte