Forum Discussion

webster_ben's avatar
webster_ben
Novice I
2 years ago
Solved

Is there a way to disable csi migration features?

is there a way to disable csi migration features from the kube-controller-manager deployed by portworx? our clusters KCM is fighting with portworx's attempting to migrate vsphere volumes in our clusters

automation
containers
kubernetes
PLATFORM ENGINEERING
PORTWORX DATA SERVICES
PX-DR
PX-ENTERPRISE
  • webster_ben's avatar
    webster_ben
    2 years ago
    Supports recommendation was to disable the pvc controller with the annotation ```http://portworx.io/pvc-controller|portworx.io/pvc-controller: "false"``` which does appear to have resolved the issue.
  • ccrow's avatar
    ccrow
    Moderator
    2 years ago
    Yeah, I know there are conflicts with that version. I don't think there is a way to change the KCM via our spec. I also saw your backup question come through. Let me see if I can have someone jump on to comment more completely.
  • webster_ben's avatar
    webster_ben
    Novice I
    2 years ago
    This stems from a support case with Red Hat regarding two of our testing clusters that we recently upgraded to Openshift 4.12 that have portworx installed on them, our in tree vsphere pvs are having migration labels added and removed constantly, our 4.11 clusters remain unaffected, in 1.25 I believe the vsphere csi migration feature gate is enable by default, where as in openshift this feature does not get enabled by default until 4.13 which is based on kubernetes 1.26 (and even then if you upgrade to 4.13 from a lower version, it remains opt-in)
  • webster_ben's avatar
    webster_ben
    Novice I
    2 years ago
    Supports recommendation was to disable the pvc controller with the annotation ```http://portworx.io/pvc-controller|portworx.io/pvc-controller: "false"``` which does appear to have resolved the issue.