Description of problem: On azure PV region node affinity is failure-domain.beta.kubernetes.io instead of topology.kubernetes.io, on aws and gcp they are topology.kubernetes.io. Based on https://kubernetes.io/docs/reference/labels-annotations-taints/#failure-domainbetakubernetesiozone, Starting in v1.17, this label failure-domain.beta.kubernetes.io is deprecated in favor of topology.kubernetes.io/zone. Version-Release number of selected component (if applicable): 4.8.0-0.nightly-2021-06-14-145150 How reproducible: always Steps to Reproduce: 1. Create a pvc apiVersion: v1 kind: PersistentVolumeClaim metadata: name: pvc spec: accessModes: - ReadWriteOnce resources: requests: storage: 1Gi 2. Create a pod apiVersion: v1 kind: Pod metadata: name: task-pv-pod spec: volumes: - name: task-pv-storage persistentVolumeClaim: claimName: pvc containers: - name: task-pv-container image: nginx ports: - containerPort: 80 name: "http-server" volumeMounts: - mountPath: "/usr/share/nginx/html" name: task-pv-storage 3. Check pv node affinity oc describe pv pvc-ffa7bc8c-d68e-4161-9efd-4b0ac2cc17a6 Node Affinity: Required Terms: Term 0: failure-domain.beta.kubernetes.io/region in [northcentralus] Actual results: The node affinity is failure-domain.beta.kubernetes.io instead of topology.kubernetes.io Expected results: The node affinity is topology.kubernetes.io Additional info:
This will be fixed in Kubernetes 1.22 in https://github.com/kubernetes/kubernetes/pull/101534 / OCP 4.9 failure-domain.beta.kubernetes.io labels are still working in 4.8
Clearing the target release, we do not fix low prio bugs at this stage of 4.8 release.
Using low priority as signal for "waiting for rebase".
Kubernetes rebase has landed.
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Moderate: OpenShift Container Platform 4.10.3 security update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHSA-2022:0056