What you think should happen instead? Pods should get unique names How to reproduce Upgrade to Bitnami chart version from 13.1.1 to 19.0.3 Operating System Debian GNU/Linux 12 Versions of Apache Airflow Providers 2.10 Deployment Official Apache Airflow Helm Chart Deployment details Helm deployment ...
In Bitnami Premium, all of the applications are built on Debian just as they are in the free Bitnami library. You get the entire library of containers and Helm charts kept up-to-date with the latest changes anywhere in each app from the OS to the application code itself. You can consume...
To install Helm, refer to the Helm install guide and ensure that the helm binary is in the PATH of your shell.Using HelmOnce you have installed the Helm client, you can deploy a Bitnami Helm Chart into a Kubernetes cluster.Please refer to the Quick Start guide if you wish to get ...
In Bitnami Premium, all of the applications are built on Debian just as they are in the free Bitnami library. You get the entire library of containers and Helm charts kept up-to-date with the latest changes anywhere in each app from the OS to the application code itself. You can consume...
- -https://charts.bitnami.com/bitnami/airflow-18.3.2.tgz + - oci://registry-1.docker.io/bitnamicharts/airflow:18.3.2 Users should not see any change for deploying Helm charts. The requirement is to use a Helm CLI greater than 3.8.0 to deploy them. ...
Are you able to reproduce the issue when installing the Helm chart by simply runninghelm install airflow oci://registry-1.docker.io/bitnamicharts/airflow? If that deployment succeeds, what happens when you use your custom valueshelm install airflow oci://registry-1.docker.io/bitnamicharts/air...
Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files. Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm Title of the pull request follows this pattern [bitnami/<name_...
Chart version bumped in Chart.yaml according to semver. This is not necessary when the changes only affect README.md files. Variables are documented in the values.yaml and added to the README.md using readme-generator-for-helm Title of the pull request follows this pattern [bitnami/<name_...
[bitnami/redis-cluster] Request to Increase Default terminationGracePeriodSeconds for Redis StatefulSet in Helm Chartfeature-requestredis-clustertriageTriage is needed #30412 openedNov 12, 2024bysajad-sadra 3 [bitnami/airflow] load custom dags on airflowairflowtech-issuesThe user has a technical issu...
bitnami/airflow 17.2.4 What architecture are you using? None What steps will reproduce the bug? Installing the chart with following values: dags:existingConfigmap:"dags" Are you using any custom parameters or values? No response What is the expected behavior?