Customer has installed IPI VSphere. The customer added a Power node, and we found that VSphere improperly tried to scheduling pods on Power.

When using the `multi` payload, it uses the release images - https://mirror.openshift.com/pub/openshift-v4/multi/clients/ocp/4.17.15/ppc64le/release.txt which include these images:

```
vsphere-cloud-controller-manager quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:1967ade4383c4a694fc03f4e06e65e69f5e8f8e39afe0398f01a435e6dc119d2
vsphere-cluster-api-controllers quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:8dd0148db1bed35901f8bc15cdd2ae1602d91958bc992c0ed399a70b7805b9ff
vsphere-csi-driver quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:f7af5d13e86e0ba3d61282a237f000f7a003ba88459b1777b2bfba66430b9c6b
vsphere-csi-driver-operator quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:b4628bf778520b6790c1515e317d48cb91665b602efa574cbb29c37872d3bd61
vsphere-csi-driver-syncer quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:0760edad374996ed026be276b887a3146e4bd90e22f1dca44845d444587b33fd
vsphere-problem-detector quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:98cd8b048ac314c79963d91c67824bd63e4360ff1d6d77d2ba1a5c3e359d4729
```

You can see the release payload declaring various architectures - it should only claim the architectures it's actually built for...

```
❯ crane manifest quay.io/openshift-release-dev/ocp-v4.0-art-dev@sha256:17bd8919a43745edee1c4ca8d10582ccf2bb8669115b643269b9337ec2b9cd90 | jq -r '.manifests[].platform.architecture'
amd64
ppc64le
s390x
arm64
```

When the node tries to load on the Power image, it tries to execute an executable and enters CrashLoopBackOff.

We caught this while using the Multi-Arch Tuning Operator

We'd like to update this https://github.com/openshift/vmware-vsphere-csi-driver-operator/blob/main/assets/node.yaml#L33 to include only the support arches.

This is related to a customer dev environment.