Skip to content

kubernetes: pin the RetryOnFailure strategy on the Proxmox csi release #4731

Closed

Description

packages/apps/kubernetes/templates/helmreleases/csi-proxmox.yaml sets strategy.name: RetryOnFailure on install and upgrade, like csi.yaml and cilium.yaml, but only the KubeVirt pair is pinned (cilium_install_retry_test.yaml, csi_install_retry_test.yaml). Nothing reads the Proxmox one today, because the e2e HelmRelease guard runs only on the KubeVirt substrate. So this is a gap to close before the Proxmox suite starts reusing that guard, not a live defect. A case in substrate_proxmox_addons_test.yaml asserting the strategy on both actions is enough.

Activity

  1. themoriarti commented on Oct 19, 2026

    @themoriarti
    Collaborator

    Fix in #4969: the mirror test csi_proxmox_install_retry_test.yaml pins RetryOnFailure on both actions of the Proxmox csi release, and the guard comment that pointed at the gap is updated. No template change.

  2. added
    triage/acceptedIndicates an issue is ready to be actively worked on
    and removed
    triage/needs-triageIndicates an issue needs triage by a maintainer
    on Oct 19, 2026
  3. themoriarti commented on Oct 28, 2026

    @themoriarti
    Collaborator
  4. added a commit that references this issue on Oct 28, 2026
    ae9e7c4
  5. added a commit that references this issue on Nov 1, 2026
    98d0402
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Labels

kind/cleanupCategorizes issue or PR as related to cleanup of code, process, or technical debttriage/acceptedIndicates an issue is ready to be actively worked on

Type

No type

Projects

No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions