Found new issue where if there is a default storageclass (i.e. gp2) then the registry PV is claimed from this SC instead of creating gluster volume and mounting to registry POD(s).
Options below were used. The registry POD did get correctly scheduled on the one infra node available but the volume was claimed from SC=gp2 which is created as default SC if cloud_provider_kind=aws.
Found new issue where if there is a default storageclass (i.e. gp2) then the registry PV is claimed from this SC instead of creating gluster volume and mounting to registry POD(s).
Options below were used. The registry POD did get correctly scheduled on the one infra node available but the volume was claimed from SC=gp2 which is created as default SC if cloud_provider_kind=aws.