Skip to content

ArgoCD ignores Helm reclaim policy and does not persist scratch area #1227

@DiamondJoseph

Description

@DiamondJoseph

As observed on p46, which only has a scratch-1.4.1 PVC and not the prior scratch-1.4.0 PVC after upgrading. We want to preserve the PVC for a limited time to persist code changes across restarts but also to allow rolling back and grant time to push changes up to remote.

May be due to
https://www.reddit.com/r/ArgoCD/comments/12hl6ob/helmshresourcepolicy_keep_is_getting_ignored_in/

Acceptance Criteria

  • PVC deletion behaviour is as expected and documented in the Helm chart

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions