Skip to content

incorrect helm chart validation for apiServer.env field #51190

@LucasRoesler

Description

@LucasRoesler

Official Helm Chart version

main (development)

Apache Airflow version

3.0.0

Kubernetes Version

1.31

Helm Chart configuration

airflowVersion: 3.0.0
apiServer:
  env:
    - name: AIRFLOW__CORE__SIMPLE_AUTH_MANAGER_ALL_ADMINS
      value: "true"
    - name: AIRFLOW__API_AUTH__JWT_SECRET
      valueFrom:
        secretKeyRef:
          name: airflow-webserver-secret
          key: webserver-secret-key

Docker Image customizations

No response

What happened

I am currently trying to deploy the latest Airflow. During deployment I ran into an issue with AIRFLOW__API_AUTH__JWT_SECRET not being set. This is already reported here #50538

To work around this I decided to pass a custom env variable via the apiServer.env value. Because this is a secret value, I wanted to use a valueFrom configuration. This is supported by the other components, like webserver and th same implementation is used by the templates, however, when executing helm, it produces the following validation error

Error: values don't meet the specifications of the schema(s) in the following chart(s):
airflow:
- apiServer.env.1: value is required
- apiServer.env.1: Additional property valueFrom is not allowed

What you think should happen instead

The template supports this feature, only the values.schema.json needs to be updated, copying the configuration used for the other components.

I have already validated that the chart works, once the schema is updated. I am prepared to submit a PR, if it is allowed.

How to reproduce

You can reproduce using the provided values file and then in the airflow repository run

$ helm template local ./chart --values bug-values.yaml

Anything else

No response

Are you willing to submit PR?

  • Yes I am willing to submit a PR!

Code of Conduct

Metadata

Metadata

Assignees

No one assigned

    Labels

    area:helm-chartAirflow Helm Chartkind:bugThis is a clearly a bugneeds-triagelabel for new issues that we didn't triage yet

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions