AKS multi zone configuration issue - pod affinity/anti-affinity - closed

AKS in multi zone deployment
the pod/portworx-pvc-controlle dose not deployed. looks like this is an issue with PVC and deferent avilability zones.
kubectl describe pod/portworx-pvc-controller-69bfd4cd74-k8w5v -n kube-system

Warning FailedScheduling 4m1s (x3 over 5m29s) default-scheduler 0/1 nodes are available: 1 node(s) didn’t match pod affinity/anti-affinity, 1 node(s) didn’t match pod anti-affinity rules.
Warning FailedScheduling 3m48s (x2 over 3m57s) default-scheduler 0/2 nodes are available: 1 node(s) didn’t match pod affinity/anti-affinity, 1 node(s) didn’t match pod anti-affinity rules, 1 node(s) had taint {node.kubernetes.io/not-ready: }, that the pod didn’t tolerate.
Normal NotTriggerScaleUp 18s (x31 over 5m19s) cluster-autoscaler pod didn’t trigger scale-up: 1 max node group size reached
Warning FailedScheduling 1s (x5 over 3m38s) default-scheduler 0/2 nodes are available: 2 node(s) didn’t match pod affinity/anti-affinity, 2 node(s) didn’t match pod anti-affinity rules.