https://linen.dev logo
Join Slack
Powered by
<@U04S8PLJWMT> How do I increase the PVC for the m...
# ask-ai
a
@kapa.ai How do I increase the PVC for the minio pod?
k
To increase the Persistent Volume Claim (PVC) for the Minio pod in Airbyte, you can modify the 
values.yaml
file in your Helm chart configuration. Here's how you can do it: 1. Locate your 
values.yaml
file for the Airbyte Helm chart. 2. Find the Minio section in the file. It should look similar to this:
Copy code
yaml minio:   enabled: true   auth:     rootUser: minio     rootPassword: minio123   storage:     volumeClaimValue: 500Mi
3. Increase the 
volumeClaimValue
to your desired size. For example, to increase it to 5Gi:
Copy code
yaml minio:   enabled: true   auth:     rootUser: minio     rootPassword: minio123   storage:     volumeClaimValue: 5Gi
4. Save the 
values.yaml
file and upgrade your Helm release with the new configuration. It's important to note that increasing the PVC size may not automatically expand the existing volume. You might need to manually expand the underlying storage or recreate the PVC for the changes to take effect. If you're using a version of Airbyte that doesn't include Minio in the Helm chart (as mentioned in some of the knowledge sources), you may need to configure external storage instead. For more detailed information on configuring storage in Airbyte, you can refer to the [Implementation Guide](https://docs.airbyte.com/enterprise-setup/implementation-guide#configuring-external-logging) in the Airbyte documentation.
a
Where can I find the minio chart?
@kapa.ai Why isn't the minio PVC value being used by Airbyte?
k
A message from kapa.ai
Based on the knowledge sources provided, there are a few potential reasons why the Minio PVC value might not be used by Airbyte as expected: 1. Outdated values.yaml file: According to [Github Issue #49843](https://github.com/airbytehq/airbyte/issues/49843), using an outdated 
values.yaml
file can cause problems with configurations not being applied correctly. The Airbyte team recommends using a minimal values file instead of copying and modifying the full version, as changes may not be compatible across versions. 2. Configuration override issue: As mentioned in the [Implementation Guide](https://docs.airbyte.com/enterprise-setup/implementation-guide#customizing-your-deployment), you need to create an additional 
values.yaml
file to override specific configurations. Make sure you're using the correct syntax and structure in your override file. 3. Version-specific changes: The Minio configuration might have changed in different versions of Airbyte. For example, in [Github Issue #36801](https://github.com/airbytehq/airbyte/issues/36801), it was noted that Minio does not appear when installing with 'helm' from version 0.39.17 onwards. 4. Incorrect configuration path: Ensure that you're using the correct configuration path in your 
values.yaml
file. The structure might have changed in recent versions. 5. External storage configuration: If you've configured Airbyte to use external storage (like S3) instead of Minio, the Minio PVC settings might be ignored. To troubleshoot this issue, you could: 1. Check your Airbyte version and ensure you're using the correct configuration structure for that version. 2. Verify that your 
values.yaml
override file is being applied correctly during the Helm upgrade/install process. 3. Check the Airbyte logs for any error messages related to storage configuration. 4. Ensure that you haven't inadvertently configured external storage that's overriding the Minio settings. If the problem persists, you might want to open a new issue on the Airbyte GitHub repository with your specific configuration and version details, as suggested by an Airbyte team member in one of the issues.
4 Views
Open in Slack
PreviousNext
Powered by