STOR-1767: add env var OPERATOR_NAME to vsphere csi operator deployment#485
Conversation
openshift/vmware-vsphere-csi-driver-operator#233 will do `allowOperatorRemovedState=True` for vsphere csi operator. This will trigger finalazer check in library-go: ``` if management.IsOperatorRemovable() { if err := v1helpers.EnsureFinalizer(ctx, c.operatorClient, c.name); err != nil { ``` `EnsureFinalizer()`, in turn, calculates finalizer name either as `os.Getenv("OPERATOR_NAME")` or `os.Args[0]`. The latter doesn't work for vsphere because leading slash in `/usr/bin/vmware-vsphere-csi-driver-operator` is not allowed: ``` E0701 19:43:32.342151 1 base_controller.go:268] VMwareVSphereDriverControllerServiceController reconciliation failed: ClusterCSIDriver.operator.openshift.io "csi.vsphere.vmware.com" is invalid: metadata.finalizers: Invalid value: "/usr/bin/vmware-vsphere-csi-driver-operator.operator.openshift.io/VMwareVSphereDriverControllerServiceController": a qualified name must consist of alphanumeric characters, '-', '_' or '.', and must start and end with an alphanumeric character (e.g. 'MyName', or 'my.name', or '123-abc', regex used for validation is '([A-Za-z0-9][-A-Za-z0-9_.]*)?[A-Za-z0-9]') with an optional DNS subdomain prefix and '/' (e.g. 'example.com/MyName') ```
|
@mpatlasov: This pull request references STOR-1767 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: mpatlasov The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@mpatlasov: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here. |
|
/lgtm |
|
/label docs-approved |
|
/label no-qe |
|
@mpatlasov: The label(s) DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. |
|
/label qe-approved |
|
@mpatlasov: This pull request references STOR-1767 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[ART PR BUILD NOTIFIER] This PR has been included in build ose-cluster-storage-operator-container-v4.17.0-202407030818.p0.g5c50083.assembly.stream.el9 for distgit cluster-storage-operator. |
openshift/vmware-vsphere-csi-driver-operator#233 will do
allowOperatorRemovedState=Truefor vsphere csi operator. This will trigger finalazer check in library-go:EnsureFinalizer(), in turn, calculates finalizer name either asos.Getenv("OPERATOR_NAME")oros.Args[0]. The latter doesn't work for vsphere because leading slash in/usr/bin/vmware-vsphere-csi-driver-operatoris not allowed: