Helm Schema Validation Prevents Specifying Custom Executors

[chrisfregly]

Official Helm Chart version

1.18.0 (latest released)

Apache Airflow version

2.11

Kubernetes Version

1.29

Helm Chart configuration

The Airflow Helm Chart provides robust schema validation, however this validation currently only allows Airflow officially supported Executors to be specified in the executor values field. See the schema here for details.

Docker Image customizations

No response

What happened

No response

What you think should happen instead

Custom executors should be allowed without the need to specify the helm --skip-schema-validation flag. One solution could be to allow any name that includes the word Executor at the end. This would loosens this validation significantly though I'm not sure how necessary this validation is to begin with. Very much open to other better solutions if anyone has them.

How to reproduce

Specifying a custom executor

executor: my.org.MyCustomExecutor

results in the following error when running helm template command:

- executor: Does not match pattern '^(LocalExecutor|LocalKubernetesExecutor|CeleryExecutor|KubernetesExecutor|CeleryKubernetesExecutor|airflow.providers.edge3.executors.EdgeExecutor|airflow.providers.amazon.aws.executors.batch.AwsBatchExecutor|airflow.providers.amazon.aws.executors.ecs.AwsEcsExecutor)(,(LocalExecutor|LocalKubernetesExecutor|CeleryExecutor|KubernetesExecutor|CeleryKubernetesExecutor|airflow.providers.edge3.executors.EdgeExecutor|airflow.providers.amazon.aws.executors.batch.AwsBatchExecutor|airflow.providers.amazon.aws.executors.ecs.AwsEcsExecutor))*$'

Anything else

No response

Are you willing to submit PR?

• Yes I am willing to submit a PR!

Code of Conduct

• I agree to follow this project's Code of Conduct

[boring-cyborg]

Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.