Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

🐛 Fix Helm Charts: add a storage class name for Min IO #379

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

espados
Copy link

@espados espados commented Dec 19, 2024

What

Adding a storage class label in helm charts for airbyte with Min IO because without no storage class name & no default set, it throws this error.
no persistent volumes available for this claim and no storage class is set

How

A section has been added in the minio.yaml file in the airbyte templates where the storageClassName would be set only if a value has been passed.

Recommended reading order

  1. minio.yaml
  2. values.yaml

Can this PR be safely reverted and rolled back?

  • YES 💚
  • NO ❌

@CLAassistant
Copy link

CLAassistant commented Dec 19, 2024

CLA assistant check
All committers have signed the CLA.

espados and others added 3 commits December 19, 2024 22:47
## What
<!--
* Describe what the change is solving.
* It helps to add screenshots if it affects the frontend.
-->

Issue: airbytehq/airbyte#54176

Current Helm `values.yml` documentation and defaults have old unused
values for `externalDatabase`, potentially leading to confusion when
setting up or upgrading Helm chart versions.

## How
<!--
* Describe how code changes achieve the solution.
-->

This removes `externalDatabase` from all defaults and documentation.
These values are not used anywhere in the project outside of the changes
files in this PR. Instead `global.database` should be used instead to
configure external PostgreSQL connections.

## Can this PR be safely reverted and rolled back?
<!--
* If you know that your be safely rolled back, check YES.*
* If that is not the case (e.g. a database migration), check NO.
* If unsure, leave it blank.*
-->
- [x] YES 💚
- [ ] NO ❌

Co-authored-by: perangel <[email protected]>
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants