Skip to content

Add NodePort Option to the values schema #26812

@joseph-max-coalfire

Description

@joseph-max-coalfire

Official Helm Chart version

1.6.0 (latest released)

Apache Airflow version

2.3.4

Kubernetes Version

1.23

Helm Chart configuration

# 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

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Labels

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions