uplsh580 commented on issue #60668: URL: https://github.com/apache/airflow/issues/60668#issuecomment-3764231734
It seems the YAML configuration you shared (apiServer.env) is strictly for injecting environment variables into the apiServer pod itself. Since these variables are defined at the container level for a specific component, they are not parsed into the kubernetes_environment_variables section of the Airflow configuration (which is typically used for worker pods). Therefore, this specific part might not be the root cause of the UI exposure issue. If you are not using the `config.kubernetes_environment_variables` section or the `AIRFLOW__KUBERNETES_ENVIRONMENT_VARIABLES__` prefix anywhere else, it is quite puzzling how those values are being populated in that specific section. From what I can see, I'm at a loss to explain this behavior further with the current information. It might be a deeper issue with how Airflow 3.x handles configuration internally, or perhaps there's another hidden source of configuration I'm missing. -- 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]
