-
Notifications
You must be signed in to change notification settings - Fork 479
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
feat: add airflow.extraPodSpec
value
#806
base: main
Are you sure you want to change the base?
Conversation
Signed-off-by: Romain Boutinaud <[email protected]>
This issue has been automatically marked as stale because it has not had activity in 60 days. Thank you for your contributions. Issues never become stale if any of the following is true:
|
Bumping for bot. |
I am not sure this is a good idea, it will result in people breaking stuff and anyone who has such complex requirements can probably just fork the chart for their own purposes. @Hosade Am I missing anything that might make this necessary? |
airflow.extraPodSpec
value
Hi, necessary, I don't know. Forking (and maintaining the fork) for something that simple is kind of a pain. This would not break any existing setup and does not seem to be more error prone than other k8s concepts that we can find in the chart (pdb, affinity...) |
This issue has been automatically marked as stale because it has not had activity in 60 days. Thank you for your contributions. Issues never become stale if any of the following is true:
|
What issues does your PR fix?
Ability to add misc. spec resources on pods
What does your PR do?
Add a extraPodSpec variable to allocate Spec of pods not anticipated by the chart.
Checklist
For all Pull Requests
For releasing ONLY