Closed dabukster closed 10 months ago
Thanks for opening your first issue here! Be sure to follow the issue template! If you are willing to raise PR to address this issue please do so, no need to wait for approval.
Can you please provide us with the custom-values.yaml
you're using? Or at least, what you think is, the relevant part out of it?
It's look like a problem in the first initContainer in each pod, that mean the wait-for-airflow-migrations
.
I see that u added dbMigrations
in your values (just be notice the comments for it are wrong, you are describing there the worker) therefore I cannot template your chart.
Can you run helm template
and upload the result or add the your chart here?
I just added the dbMigrations section as the k8s cluster complained about it. Thus, just remove it. But I assume it is due to the configuration of our k8s cluster, as I just use the standard configuration and added the resource limits. Am 04.12.2023 um 18:52 schrieb rom sharon @.***>: It's look like a problem in the first initContainer in each pod, that mean the wait-for-airflow-migrations. I see that u added dbMigrations in your values (just be notice the comments for it are wrong, you are describing there the worker) therefore I cannot template your chart. Can you run helm template and upload the result or add the your chart here?
—Reply to this email directly, view it on GitHub, or unsubscribe.You are receiving this because you authored the thread.Message ID: @.***>
This issue has been automatically marked as stale because it has been open for 14 days with no response from the author. It will be closed in next 7 days if no further activity occurs from the issue author.
This issue has been closed because it has not received response from the issue author.
Official Helm Chart version
1.11.0 (latest released)
Apache Airflow version
8.8.0
Kubernetes Version
1.25.11
Helm Chart configuration
No response
Docker Image customizations
No response
What happened
I want to install Airflow on a kubernetes cluster. Background, the cluster is provided by our department, so I can't change anything about the settings.
When I run
helm install ... --values custom-values.yaml ...
I get for all components the same error message (cf. below), even though I tried to addrequests/limits
entries to theresources
sections andrunAsNonRoot
insecurityContext
sections in acustom-values.yaml
. But it seems these values are ignored.Question: How can I provide these values or how can I adjust the configuration to get installation running?
Comment: The same issue was also raised for the community helm chart, but got never addressed as well
What you think should happen instead
The helm chart should be installed
How to reproduce
Install on a kubernetes cluster with kyverno in place that enforces the restrictions returned by the error messages.
Anything else
No response
Are you willing to submit PR?
Code of Conduct