SaveCodeHere opened a new issue, #50025:
URL: https://github.com/apache/airflow/issues/50025
### Apache Airflow version
3.0.0
### If "Other Airflow 2 version" selected, which one?
3.0.0
### What happened?
After switching our environment airflow 3.0.0, the kubernetesexecutor
worker forces an init-container with busybox image.
Our environment is walled off and we do not have access to outside
resources, thus, all airflow executors now fails on start-up with the init.
I propose two solutions
1. Add config option to change and/or overwrite the forced init-container
configuration
2. . Add config option to skip the forced init-container all together
### What you think should happen instead?
it should not force an init container that makes walled off environment fail
after 3.0.0 upgrade
### How to reproduce
Start a dag with kubernetes executor in kubernetes environment
### Operating System
Debian bookworm 12.10
### Versions of Apache Airflow Providers
_No response_
### Deployment
Other Docker-based deployment
### Deployment details
Openshift/Kubernetes deploy
### Anything else?
_No response_
### Are you willing to submit PR?
- [ ] 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]
