Kay Burdeos
10/27/2024, 1:47 AMuser
10/27/2024, 1:47 AMvalues.yaml
file used in your Helm deployment. Here's how you can do it: 1. In your values.yaml
file, update the storage configuration section. Set the authenticationType
to instanceProfile
. Here's an example of how it might look: yaml global: storage: type: "GCS" # or "S3" if you're using AWS storageSecretName: airbyte-config-secrets bucket: log: airbyte-bucket state: airbyte-bucket workloadOutput: airbyte-bucket gcs: # or s3 if using AWS projectId: <project-id> authenticationType: instanceProfile
2. Ensure that your compute infrastructure (e.g., EC2 instances or Kubernetes nodes) has the appropriate IAM role attached with permissions to read and write to the specified buckets. 3. After making these changes to your values.yaml
file, you can upgrade your Helm release using the following command: helm upgrade --namespace airbyte --values ./values.yaml --install [RELEASE_NAME] --version [RELEASE_VERSION] airbyte/airbyte
Replace [RELEASE_NAME]
with your current release name and [RELEASE_VERSION]
with the version you're upgrading to. [Source: Upgrading on K8s using Helm](https://docs.airbyte.com/operator-guides/upgrading-airbyte#upgrading-on-k8s-using-helm) It's important to note that when making such changes, you should be cautious and test the changes in a non-production environment first. Also, ensure that you've properly configured your Kubernetes secrets and IAM roles as mentioned in the [implementation guide prerequisites](https://docs.airbyte.com/enterprise-setup/implementation-guide#configure-kubernetes-secrets). Remember, this change will affect how Airbyte authenticates to your storage service for logging purposes. Make sure your infrastructure is properly set up to support this authentication method before applying the changes.Kay Burdeos
10/27/2024, 1:48 AMuser
10/27/2024, 1:48 AM