chrisfregly opened a new issue, #54673: URL: https://github.com/apache/airflow/issues/54673
### 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](https://github.com/apache/airflow/blob/main/chart/values.schema.json#L690). ### 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 ```yaml 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? - [x] Yes I am willing to submit a PR! ### Code of Conduct - [x] I agree to follow this project's [Code of Conduct](https://github.com/apache/airflow/blob/main/CODE_OF_CONDUCT.md) -- 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]
