Trying to update to Airbyte 1.0 but I get this:

ERROR   Failed to install airbyte/airbyte Helm Chart
  ERROR   Unable to install Airbyte locally
  ERROR   unable to install airbyte chart: unable to install helm: YAML parse error on airbyte/charts/server/templates/deployment.yaml: error converting YAML to JSON: yaml: line 256: could not find expected ':'

New message text here

@kapa.ai From trial and error I have found out that it works if I remove the storage-section from values.yaml. Any idea why?

The

values.yaml

file is used to configure your Airbyte deployment on Kubernetes. The

storage

section in this file is typically used to specify the type of storage to be used (like S3, GCS, or MinIO), and other related configurations. If removing the

storage

section from the

values.yaml

file makes your deployment work, it could be due to a few reasons: 1. Incorrect Configuration: The

storage

section might have been incorrectly configured. For instance, you might have specified an unsupported storage type or provided incorrect access keys or bucket names for S3 or GCS storage. 2. Deprecated Configuration: If you're migrating from an old chart to Airbyte v0.52.0 and the latest chart version, you're advised to remove any deprecated storage and secrets manager environment variables related to S3 and AWS Secrets Manager from your

values.yaml

or

airbyte-pro-values.yaml

files ([source](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#migration-steps-1)). 3. Conflicts with Other Settings: The

storage

settings might be conflicting with other settings in your

values.yaml

file. For example, if you're using an external database or MinIO setup, certain

storage

configurations might not be applicable. 4. Issues with the Storage Provider: There might be issues with the storage provider you're trying to use. For example, there have been reported issues with using external MinIO ([source](https://github.com/airbytehq/airbyte/issues/34512)) and issues with MinIO statefulset not working properly ([source](https://github.com/airbytehq/airbyte/issues/36801)). Without more specific details about your

values.yaml

file and the exact error messages you're encountering, it's hard to pinpoint the exact reason. However, these are some possible explanations based on the information available.

@kapa.ai Can you give an example of how the section could look like with S3? My setup worked prior to Airbyte 1.0

A message from kapa.ai

Sure, here's an example of how the

values.yaml

file could look like when configuring S3 as your storage option:

yaml global:     storage:       type: "S3"       storageSecretName: airbyte-config-secrets # Name of your Kubernetes secret.       bucket: # S3 bucket names that you've created. We recommend storing the following all in one bucket.         log: airbyte-bucket         state: airbyte-bucket         workloadOutput: airbyte-bucket       s3:         region: "" # e.g. us-east-1         authenticationType: credentials # Use "credentials" or "instanceProfile"

In the

server

block, you would also need to add the following:

yaml server:     extraEnv:       - name: AWS_ACCESS_KEY_ID         valueFrom:           secretKeyRef:             name: airbyte-logs-secrets             key: AWS_KEY       - name: AWS_SECRET_ACCESS_KEY         valueFrom:           secretKeyRef:             name: airbyte-logs-secrets             key: AWS_SECRET_KEY       - name: STATE_STORAGE_S3_ACCESS_KEY         valueFrom:           secretKeyRef:             name: airbyte-logs-secrets             key: AWS_KEY       - name: STATE_STORAGE_S3_SECRET_ACCESS_KEY         valueFrom:           secretKeyRef:             name: airbyte-logs-secrets             key: AWS_SECRET_KEY       - name: STATE_STORAGE_S3_BUCKET_NAME         valueFrom:           secretKeyRef:             name: airbyte-logs-secrets             key: S3_LOG_BUCKET       - name: STATE_STORAGE_S3_REGION         valueFrom:           secretKeyRef:             name: airbyte-logs-secrets             key: S3_LOG_BUCKET_REGION

Please replace the placeholders with your actual AWS S3 bucket name, region, and the names of your Kubernetes secrets that store your AWS access keys. After updating your

values.yaml

file, you can apply the changes by running the following command:

bash helm upgrade --install %RELEASE_NAME% airbyte/airbyte -n <NAMESPACE> --values /path/to/values.yaml --version 0.50.13

Replace

%RELEASE_NAME%

with the name of your Helm release,

<NAMESPACE>

with the Kubernetes namespace where you're deploying Airbyte, and

/path/to/values.yaml

with the path to your

values.yaml

file. Please note that these instructions are based on the [Airbyte documentation](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#external-logs-with-s3) and may need to be adjusted based on your specific setup and requirements.