calebwoofenden opened a new issue, #27037:
URL: https://github.com/apache/airflow/issues/27037
### Official Helm Chart version
1.6.0 (latest released)
### Apache Airflow version
2.3.2
### Kubernetes Version
1.21
### Helm Chart configuration
I'm using this chart as a subchart. In my Chart.yaml I have:
```
dependencies:
- name: airflow
version: 1.6.0
repository: "https://airflow.apache.org/";
```
then in my chart I define a values file that sets some helm values,
including overriding some values for the airflow chart:
```
airflow:
# this doesn't seem to work :/
logs:
persistence:
storageClassName: gp3
enabled: false
size: 10Gi
```
### Docker Image customisations
_No response_
### What happened
I download the helm dependency and install my chart. I've overridden other
values under `airflow` like `images.airflow.repository` and
`images.airflow.tag` and those work fine.
However, the `logs` values seem to not work. I set
`logs.persistence.enabled` to `false` which should disable the logs PVC, but I
continue to see a PVC get created called `logs-<my helm release
name>-scheduler-0`, and it ignores the `storageClassName` I'm passing, which
causes it to get stuck in a pending state. The `<my helm release
name>-scheduler-0` pod relies on this PVC.
I'm not entirely convinced that this PVC is the one created in
`charts/airflow/templates/logs-persistent-volume-claim.yaml` since it should be
named `{{ airflow_logs_volume_claim }}`, which is defined as follows:
```
{{ define "airflow_logs_volume_claim" -}}
{{- if .Values.logs.persistence.existingClaim -}}
{{ .Values.logs.persistence.existingClaim }}
{{- else -}}
{{ .Release.Name }}-logs
{{- end -}}
{{- end -}}
```
This would make me think the PVC would be named `<my helm release
name>-logs`, not `logs-<my helm release name>-scheduler-0`. However, I don't
see any other PVC definitions in the chart that can explain that name.
### What you think should happen instead
_No response_
### How to reproduce
Create a helm chart with this airflow chart as a child chart (listed under
dependencies). Try to set `airflow.logs.persistence.enabled` or
`airflow.logs.persistence.storageClassName`. Note that the logs PVC that gets
created ignores these values in favor of the defaults of `true` and `100Gi`
respectively.
### Anything else
_No response_
### Are you willing to submit PR?
- [ ] Yes I am willing to submit a PR!
### Code of Conduct
- [X] I agree to follow this project's [Code of
Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md)
--
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
To unsubscribe, e-mail: [email protected]
For queries about this service, please contact Infrastructure at:
[email protected]
