Skip to content

Conversation

@rvdh
Copy link

@rvdh rvdh commented Jul 2, 2025

  • Signed off your work as per the DCO.
  • Add unit-tests

What this PR does / why we need it:
This PR adds three parameters to the Portworx helm chart:

  • annotations: to set annotations on the StorageCluster object
  • imagePullPolicy: to set the imagePullPolicy for PX pods
  • priorityClassName: to set PriorityClassName to be passed to Podspec of px pods for it to be scheduled accordingly

| `updateStrategy.minReadySeconds` | Minimum number of seconds that a pod should be ready before the next batch of pods is updated during a rolling update | 1 |
| `updateStrategy.disruption.allow` | This field is used to enable or disable smart and parallel upgrade. Smart upgrade is disabled by default, Enable it by setting to false. we can use the `maxUnavailable` field to control the maximum number of Portworx nodes that can be upgraded at a time | None |
| `updateStrategy.autoUpdateComponents` | Specifies the update strategy for the component images. Valid values: None, Once, Always | None |
| `annotations` | Map of annotations to set on the StorageCluster object itself. | {} |
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We don't have support to add annotations directly to the stc. However, most annotations are already supported in portworx chart. Which additional annotations are we want to set on the STC ?

Copy link
Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Hi, we set the following annotations on the stc object:

# https://github.com/libopenstorage/operator/issues/354
# annotation needed to use tcr.paas.local as registry
operator.libopenstorage.org/common-image-registries: "gcr.io,k8s.gcr.io"
portworx.io/disable-storage-class: "true"

argocd.argoproj.io/sync-wave: "1"
# This resource doesn't exist yet on initial sync
argocd.argoproj.io/sync-options: SkipDryRunOnMissingResource=true

Mainly the first annotation is critical for us, to be able to use our own internal registry.

@hitesh-wani-px
Copy link
Collaborator

Please share the list of test cases or scenarios covered during testing

@rvdh
Copy link
Author

rvdh commented Jul 21, 2025

Please share the list of test cases or scenarios covered during testing

Test cases:

  • TestAnnotations
  • TestPriorityClassName
  • TestImagePullPolicy

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

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants