Natalique opened a new issue, #32581:
URL: https://github.com/apache/airflow/issues/32581
### Description
I'm using EFS For different envs in EKS and I have a few different storage
class
I need to pass airflow a templated storageClassName
Implementation
Already tested locally and all seems fine
Change in `logs-persistent-volume-claim.yaml`
From
`storageClassName: "{{ .Values.logs.persistence.storageClassName . }}"`
To
`storageClassName: "{{ tpl .Values.logs.persistence.storageClassName . }}"`
Desired content
```
apiVersion: v1
kind: PersistentVolumeClaim
metadata:
name: {{ template "airflow_logs_volume_claim" . }}
labels:
tier: airflow
component: logs-pvc
release: {{ .Release.Name }}
chart: "{{ .Chart.Name }}-{{ .Chart.Version }}"
heritage: {{ .Release.Service }}
{{- with .Values.labels }}
{{- toYaml . | nindent 4 }}
{{- end }}
{{- with .Values.logs.persistence.annotations }}
annotations: {{- toYaml . | nindent 4 }}
{{- end }}
spec:
accessModes: ["ReadWriteMany"]
resources:
requests:
storage: {{ .Values.logs.persistence.size | quote }}
{{- if .Values.logs.persistence.storageClassName }}
{{- if (eq "-" .Values.logs.persistence.storageClassName) }}
storageClassName: ""
{{- else }}
storageClassName: "{{ tpl .Values.logs.persistence.storageClassName . }}"
{{- end }}
{{- end }}
{{- end }}
```
### Use case/motivation
Templating the value of storageClassName instead of taking it as is from
values file
### Related issues
_No response_
### Are you willing to submit a 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]
