Skip to content

add priorityClassName passthrough to the helm chart #2095

Closed

Description

@JohnMastodon

the helm/volsync chart has no way to set priorityClassName on the operator pod. it exposes nodeSelector, tolerations and affinity already but not this one, so the controller sits at priority 0 no matter what

my use case: volsync runs the backups on my cluster, and on a node squeeze i don't want it to be the first pod evicted

my approach would be a small change: a priorityClassName value defaulting to "", rendered into deployment-controller.yaml next to the existing nodeSelector / affinity / tolerations blocks

i can send the PR if you're ok

Activity

  1. tesshuflower commented on Sep 8, 2026

    @tesshuflower
    Contributor

    @JohnMastodon I think this sounds reasonable if we're talking about just the VolSync controller itself, not mover pods.

    You can proceed with a PR - I think I would like to not set priorityClassName at all in the deployment yaml if not set (rather than setting to "")

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions