fix: Allow multiple Airflows in the same namespace to use Kubernetes executors (#678)

* fix: Allow multiple Airflows in the same namespace to use Kubernetes executors

* changelog

* cargo update

* Update CHANGELOG.md

Co-authored-by: Razvan-Daniel Mihai <84674+razvan@users.noreply.github.com>

---------

Co-authored-by: Razvan-Daniel Mihai <84674+razvan@users.noreply.github.com>

Author: sbernauer

CHANGELOG.md

@@ -10,10 +10,14 @@
 
 - Don't panic on invalid authorization config. Previously, a missing OPA ConfigMap would crash the operator ([#667]).
 - Fix OPA authorization for Airflow 3. Airflow 3 needs to be configured via env variables, the operator now does this correctly ([#668]).
+- Allow multiple Airflows in the same namespace to use Kubernetes executors.
+  Previously, the operator would always use the same name for the executor Pod template ConfigMap.
+  Thus when deploying multiple Airflow instances in the same namespace, there would be a conflict over the contents of that ConfigMap ([#678]).
 
 [#667]: https://github.com/stackabletech/airflow-operator/pull/667
 [#668]: https://github.com/stackabletech/airflow-operator/pull/668
 [#669]: https://github.com/stackabletech/airflow-operator/pull/669
+[#678]: https://github.com/stackabletech/airflow-operator/pull/678
 
 ## [25.7.0] - 2025-07-23