Skip to content

Add resources to migrate-db container #275

@AlissonRS

Description

@AlissonRS

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.

image

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions