Kubernetes PVC claims not adhering to AZ choice

(This could very well be my problem and not an issue with OSIE)

I created a kubernetes cluster with magnum and its up and good. When I create an application on it with persistant volume claims, it tries to use my FSD1 availability zone.

Within the OSIE Admin portal, I do NOT have Availability zones set for cinderv3 or anything at all. Is osie not adhering to that AZ setting when setting up the clusters with Magnum, or is this an openstack problem?

I am not sure if this is something that needs to be corrected when creating the cluster so it knows the AZ (‘nova’) to put its volumes, or if I just need to work with customers to have them specify the az as nova manually for every application with a PVC that they deploy.