rhps commented on issue #42136: URL: https://github.com/apache/airflow/issues/42136#issuecomment-3189974826
I've upgraded the airflow cluster on K8S to version 3.0.4. The airflow itself are running with `CeleryKubernetesExecutor` configuration. After I learned about how the new component interact, I found out: - `worker` need to be able to communicate to `api-server` service (was webserver on previous version), it is very specific worker will try to connect to `http://api-server:8080/execution/` - event `api-server` service that serve web UI (frontend part) need to be able to communicate also trying to connect to `http://api-server:8080/execution/` So suggestion from me: - Make sure to set this airflow configuration `AIRFLOW__CORE__EXECUTION_API_SERVER_URL` with api-server address. In example `AIRFLOW__CORE__EXECUTION_API_SERVER_URL : http://airflow-web:8080/execution/` - Make sure to set this airflow configuration `AIRFLOW__API_AUTH__JWT_SECRET`. You can generate it by yourself 'openssl rand -base64 16'. In example `AIRFLOW__API_AUTH__JWT_SECRET: 'ykJsrdqOKXTe14WM+zDScA=='` - Make sure airflow worker pods can communicate with api-server pods by allowing ingress/egress on your networkpolicy (if you deploy it on K8S and your cluster configuration of network policy is denied by default -- 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]
