Summary
Having trouble deploying Airbyte using the extraContainers field in the helm chart, encountering errors related to converting YAML to JSON.
Question
Hi guys!
Anyone successfuly using the “*.extraContainers” part of the helm chart?
Trying to deploy with a sidecar pattern, starting with the cron.extraContainers
followed the examples but the chart is not liking it: errors with: `error converting YAML to JSON: yaml: line 166: did not find expected key``
This topic has been created from a Slack thread to give it more visibility.
It will be on Read-Only mode here. Click here if you want
to access the original thread.
Join the conversation on Slack
["helm-chart", "extracontainers", "sidecar-pattern", "yaml-to-json", "deployment-error"]
- name: ecExample
image: <http://gcr.io/endpoints-release/my-extra-container:dev|gcr.io/endpoints-release/my-extra-container:dev>
args: [
"--listener_port=8081",
"--backend=127.0.0.1:8001",
]
ports:
- containerPort: 8081
volumeMounts:
- name: VolumeStuff
mountPath: /path/mounth
readOnly: true```
Do you mind sharing how you are configuring the extra container?
I found out <@U01MMSDJGC9>
cron:
enabled: true
replicaCount: 1
extraContainers:
- name: "sqlproxy"
image: "<http://gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.12.0|gcr.io/cloud-sql-connectors/cloud-sql-proxy:2.12.0>"
volumeMounts: []
ports:
- containerPort: 3000
args:
- "--structured-logs"
- "--address=0.0.0.0"
- "--port=3000"
- "--auto-iam-authn"
- "MY_INSTANCE"
global:
I’ll check the other charts
It need to update the chart?
yeah, it seems to be an issue only with the “cron” chart
hey <@U047LU2HAPK>
any plans to release the chart? :3
if so just let me know <@U01MMSDJGC9>
<@U047LU2HAPK> would be possible to update the Helm Chart to fix this?
its always an nindent
issue :rolling_on_the_floor_laughing:
I’ll help get this merged
It has been merged, we need to release a new version of the chart
awesome
will try to start with the other containers until we release the chart :3
Yes, let me cut a release