user
09/23/2024, 7:37 PMsecretKeyRef.name
value is invalid because it's empty. This usually means that the Kubernetes secret containing the necessary credentials for S3 hasn't been properly set up or referenced in your values.yaml
file. Here's how you can fix this: 1. Ensure that you have created a Kubernetes secret that contains your AWS credentials. The secret should include AWS_ACCESS_KEY_ID
and AWS_SECRET_ACCESS_KEY
. 2. In your values.yaml
file, you need to add extra environment variables to the worker and server blocks. These environment variables should reference the secret you created in step 1. Here's an example of how to do this: yaml worker: 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
Replace airbyte-logs-secrets
with the name of the secret you created in step 1. Do the same for the server block. 3. After updating your values.yaml
file, you can then run the Helm upgrade/install command again: bash helm upgrade --install %RELEASE_NAME% airbyte/airbyte -n <NAMESPACE> --values /path/to/values.yaml --version 0.50.13
Replace %RELEASE_NAME%
with the release name you want to use, <NAMESPACE>
with the Kubernetes namespace where you want to install Airbyte, and /path/to/values.yaml
with the path to your values.yaml
file. For more details, you can refer to the [Airbyte documentation on deploying with Kubernetes and Helm](https://docs.airbyte.com/deploying-airbyte/on-kubernetes-via-helm#external-logs-with-s3). If you're still encountering issues after following these steps, it might be helpful to share the contents of your values.yaml
file (with any sensitive information redacted) for further troubleshooting.