potiuk commented on issue #20538:
URL: https://github.com/apache/airflow/issues/20538#issuecomment-1003545756
Yeah. I looked at the templates and same case is with .affinity and
nodeSelector: it is different sequence for different types of deployments
Scheduler:
```
{{- $nodeSelector := or .Values.scheduler.nodeSelector .Values.nodeSelector
}}
{{- $affinity := or .Values.scheduler.affinity .Values.affinity }}
{{- $tolerations := or .Values.scheduler.tolerations .Values.tolerations }}
```
Triggerer:
```
{{- $nodeSelector := or .Values.nodeSelector .Values.triggerer.nodeSelector
}}
{{- $affinity := or .Values.affinity .Values.triggerer.affinity }}
{{- $tolerations := or .Values.tolerations .Values.triggerer.tolerations }}
```
Webserver:
```
{{- $nodeSelector := or .Values.webserver.nodeSelector .Values.nodeSelector
}}
{{- $affinity := or .Values.webserver.affinity .Values.affinity }}
{{- $tolerations := or .Values.webserver.tolerations .Values.tolerations }}
```
Workers:
```
{{- $nodeSelector := or .Values.nodeSelector .Values.workers.nodeSelector }}
{{- $affinity := or .Values.affinity .Values.workers.affinity }}
{{- $tolerations := or .Values.tolerations .Values.workers.tolerations }}
```
Also in `values` the only "special" case is "webserver.affinitiy" - all the
other have same - empty defaults. It seems indeed as a mistke. I cannot see why
we would like to reverse it.
--
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]
