Why architecture is different from configmap?

[Rep1AI]

As you can see https://github.com/apache/airflow-on-k8s-operator/blob/master/templates/airflow-configmap.yaml#L37 executor = KubernetesExecutor

But in it shows CeleryExecutor: https://github.com/apache/airflow-on-k8s-operator/blob/master/docs/airflow-cluster.png

Lot of confusions..

Basic questions:

• Does this operator support KubernetesExecutor?

If yes, Where is docs on installing multi node airflow with KubernetesExecutor?

[barney-s]

config map is used only if Executor type is K8s in the CRD

airflow-on-k8s-operator/controllers/airflowcluster_controller.go

Line 726 in dd430ea

bag.WithTemplate("airflow-configmap.yaml", &corev1.ConfigMapList{})

It does support it but needs some TLC and may be broken:
https://github.com/apache/airflow-on-k8s-operator/blob/master/hack/sample/mysql-k8s/cluster.yaml

[Rep1AI]

needs some TLC and may be broken

Sorry didn't understand, What is TLC? and the operator currently is not stable to use?

[GrigorievNick]

I have the same question here.
Look like, the operator does not use celery any more. But use k8s Executor.
Can some one confirm this?