K8s PVC stuck in Pending in Sydney (Dallas OK)

I'm trying to deploy a Redis container in k8s (there are a couple of other containers in my pod, but I've excluded them as I'm only having problems with PVC)

As per the question title, it gets stuck in "Pending" if I try this on a Sydney (AU) cluster, but works fine if I try against a Dallas (US) cluster. Here's the YAML:

apiVersion: v1
kind: PersistentVolumeClaim
metadata:
  name: redis-pvc
  labels:
    app: myapp
spec:
  accessModes:
    - ReadWriteOnce
  resources:
    requests:
      storage: 10Gi

---
apiVersion: apps/v1 # for versions before 1.9.0 use apps/v1beta2
kind: Deployment
metadata:
  name: redis
  labels:
    app: myapp
spec:
  selector:
    matchLabels:
      app: myapp
  strategy:
    type: Recreate
  template:
    metadata:
      labels:
        app: myapp
    spec:
      containers:
        - image: redis:6.0.8-alpine
          name: redis
          args: ['--bind', '0.0.0.0']
          ports:
            - containerPort: 6379
              name: redis
          volumeMounts:
            - name: redis-pv
              mountPath: /data
      volumes:
        - name: redis-pv
          persistentVolumeClaim:
            claimName: redis-pvc

If I kubectl apply -f redis.yaml while my k8s context is set to my Sydney cluster, and then I kubectl get pods, I see it's pending:

    $ kubectl get pods
    NAME                     READY   STATUS    RESTARTS   AGE
    redis-5c8ccbf6bb-97g2x   0/1     Pending   0          8m27s

In the output for kubectl describe pods at the end of the output, I see:

    Events:
      Type     Reason            Age   From               Message
      ----     ------            ----  ----               -------
      Warning  FailedScheduling  15s   default-scheduler  0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.
      Warning  FailedScheduling  15s   default-scheduler  0/1 nodes are available: 1 pod has unbound immediate PersistentVolumeClaims.

Now if I run through the above with my k8s context set to Dallas, everything works fine:

    $ kubectl get pods
    NAME                     READY   STATUS    RESTARTS   AGE
    redis-5c8ccbf6bb-ldhxw   1/1     Running   0          34s

Is there something wrong with Sydney?