Replies: 2 comments
-
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. |
Beta Was this translation helpful? Give feedback.
0 replies
-
Converted it into discussion as this is not Airlfow issue - just question how to work with ArgoCD - hopefully indeed someone who works with ArgoCD will help you - you can also look through issues and discussions here with ArgoCD, maybe you will find something. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
Official Helm Chart version
1.15.0 (latest released)
Apache Airflow version
2.7.1
Kubernetes Version
v1.25.12+26bab08
Helm Chart configuration
values.yaml:
Docker Image customizations
No response
What happened
I'm deploying Apache Airflow Helm Chart on our corporate environment with ArgoCD and I would love to get some help on something that I'm not being able to solve. Thanks in advance.
So far it's working pretty good, I've made some customizations to the deployment, pv's, added some jobs, etc. The problem is, when upgrading with ArgoCD, some barriers show up.
Firstly, fernet-key didn't allow upgrade on objects claiming error "missing fernet-key", so I disabled that temporarily for debug purposes. Now, everytime we commit into the branch that ArgoCD is deploying, the deploy breaks, being unable to fully sync the app, claiming errors of "Inmutable fields". I think the app is not trying to create a new updated object when we try to update, and instead is trying to modify the already existing objects. The troubleshoting I've found is just manually deleting the app and letting ArgoCD deploy it entirely again, but this way we are loosing ArgoCD automatization point.
I’m sure I’m not the only one deploying this Helm chart with ArgoCD, so I’d like to know if anyone can spot any visible errors or missing configurations. So far, I’ve followed the documentation at https://airflow.apache.org/docs/helm-chart/1.8.0/ to deploy with ArgoCD, but I might be overlooking something.
What you think should happen instead
ArgoCD should be able to update the deployment configuration and images when we push into the deployed branch.
How to reproduce
In an OpenShift cluster with ArgoCD, we deployed the official Helm chart via ArgoCD, using the configurations previously described in the values.yaml.
The deployment is successful, and the application works correctly. ArgoCD is able to deploy all objects and identify the synchronization status of the app.
We then attempt to make a change to the deployment, either by committing to the deployed branch or switching branches. The change could involve modifying a configuration or updating the image version.
Synchronization via ArgoCD fails. The only solution is to delete the deployment and let ArgoCD recreate the app from scratch.
Anything else
Thanks in advance!
Are you willing to submit PR?
Code of Conduct
Beta Was this translation helpful? Give feedback.
All reactions