We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
zone/zones are needed for k8s version v1.10 and v1.11. These two fields are deprecated in v1.12 in favor of allowedTopologies.
zone/zones
allowedTopologies
The text was updated successfully, but these errors were encountered:
ref #31
Sorry, something went wrong.
Tested allowedTopologies is supported once topology is enabled using VolumeScheduling.
VolumeScheduling
sc used for testing:
kind: StorageClass apiVersion: storage.k8s.io/v1 metadata: name: zone-sc annotations: storageclass.kubernetes.io/is-default-class: "true" provisioner: com.amazon.aws.csi.ebs volumeBindingMode: WaitForFirstConsumer allowedTopologies: - matchLabelExpressions: - key: com.amazon.aws.csi.ebs/zone values: - us-east-1b
No driver change will be needed in v1.12+ for this feature. I will add documentation for this.
leakingtapan
No branches or pull requests
zone/zones
are needed for k8s version v1.10 and v1.11. These two fields are deprecated in v1.12 in favor ofallowedTopologies
.The text was updated successfully, but these errors were encountered: