You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
# shortened values.yaml file
webserver:
service:
type: NodePort
ports:
- name: airflow-ui
port: 80
targetPort: airflow-ui
nodePort: 8081 # Note this line does not work, this is what'd be nice to have for defining nodePort
Docker Image customisations
No response
What happened
Supplying nodePort like in the above Helm Chart Configuration example fails with an error saying a value of nodePort is not supported.
What you think should happen instead
It'd be nice if we could define the nodePort we want the airflow-webserver service to listen on at launch. As it currently stands, supplying nodePort like in the above values.yaml example will fail, saying nodePort cannot be supplied. The workaround is to manually edit the webserver service post-deployment and specify the desired port for nodePort.
I looked at the way the webserver service template file is set up, and the logic there should allow this, but I believe the missing definition in the schema.json file is causing this to error out.
How to reproduce
Attempt to install the Airflow Helm chart using the above values.yaml config
Official Helm Chart version
1.6.0 (latest released)
Apache Airflow version
2.3.4
Kubernetes Version
1.23
Helm Chart configuration
Docker Image customisations
No response
What happened
Supplying nodePort like in the above Helm Chart Configuration example fails with an error saying a value of nodePort is not supported.
What you think should happen instead
It'd be nice if we could define the nodePort we want the airflow-webserver service to listen on at launch. As it currently stands, supplying nodePort like in the above values.yaml example will fail, saying nodePort cannot be supplied. The workaround is to manually edit the webserver service post-deployment and specify the desired port for nodePort.
I looked at the way the webserver service template file is set up, and the logic there should allow this, but I believe the missing definition in the schema.json file is causing this to error out.
How to reproduce
Attempt to install the Airflow Helm chart using the above values.yaml config
Anything else
No response
Are you willing to submit PR?
Code of Conduct
The text was updated successfully, but these errors were encountered: