RohithkumarRavi opened a new issue, #31394:
URL: https://github.com/apache/airflow/issues/31394
### Official Helm Chart version
1.9.0 (latest released)
### Apache Airflow version
2.5.0
### Kubernetes Version
1.25.9
### Helm Chart configuration
`
apiVersion: argoproj.io/v1alpha1
kind: Application
metadata:
name: airflow
namespace: argocd
finalizers:
- resources-finalizer.argocd.argoproj.io
labels:
name: airflow
namespace: dev
spec:
project: default
source:
repoURL: https://github.com/apache/airflow.git
targetRevision: main
path: chart
helm:
values: |
createUserJob:
useHelmHooks: false
applyCustomEnv: false
migrateDatabaseJob:
useHelmHooks: false
applyCustomEnv: false
migrateDatabaseJob:
jobAnnotations:
"argocd.argoproj.io/hook": Sync
destination:
server: https://kubernetes.default.svc
namespace: dev
syncPolicy:
automated:
prune: true
selfHeal: true
allowEmpty: false
syncOptions:
- Validate=false
- CreateNamespace=true
- PrunePropagationPolicy=foreground
- PruneLast=true
`
### Docker Image customizations
_No response_
### What happened
The above one is the ArgoCD Template which I am using to install airflow
chart using ArgoCD. I have followed the same steps mentioned in the below docs
to avoid data migration errors:
[installing-the-chart-with-argo-cd-flux-rancher-or-terraform](https://airflow.apache.org/docs/helm-chart/stable/index.html#installing-the-chart-with-argo-cd-flux-rancher-or-terraform)
Even after adding the values, I'm still getting data migration errors.
### What you think should happen instead
_No response_
### How to reproduce
Run ArgoCD on your cluster. Save the template in a .yaml file and run
**kubectl apply -f file.yaml**
### Anything else
_No response_
### Are you willing to submit PR?
- [X] 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]
