You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When using ArgoCD for deploying Flagsmith, it thinks the cluster is not synced with the chart because it finds a diff, as the migrate-db container doesn't include a resources: {}.
I understand for a migration job which is short lived adding resources may not be relevant enough, but this helps avoiding sync issues with GitOps tools, and may also avoid issues with clusters that require all workloads to have resources defined.
This affects t he deployment-api.yaml (specifically the migrate-db init container) and the jobs-migrate-db.yaml.
The text was updated successfully, but these errors were encountered:
When using ArgoCD for deploying Flagsmith, it thinks the cluster is not synced with the chart because it finds a diff, as the migrate-db container doesn't include a
resources: {}
.I understand for a migration job which is short lived adding resources may not be relevant enough, but this helps avoiding sync issues with GitOps tools, and may also avoid issues with clusters that require all workloads to have resources defined.
This affects t he
deployment-api.yaml
(specifically themigrate-db
init container) and thejobs-migrate-db.yaml
.The text was updated successfully, but these errors were encountered: