You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Using EBS volumes in a multi-AZ cluster causes problems with pods not scheduled in the same zone.
I tried to get around this by setting up different storageclasses with a topology value limiting it to a known AZ based on the name i.e.
kh-check-ew2 = topology.ebs.csi.aws.com/zone=eu-west-2a
Then I put a nodeSelector in the podSpec of the khcheck object based on the same for the nodes.
The main pod has the nodeSelector but the init/check pod don't pick up that value and therefore go into different AZ's and cannot mount the volume.
Is there anyway to get them to use the nodeSelector labels ?
Many thanks.
The text was updated successfully, but these errors were encountered:
Hi,
Using EBS volumes in a multi-AZ cluster causes problems with pods not scheduled in the same zone.
I tried to get around this by setting up different storageclasses with a topology value limiting it to a known AZ based on the name i.e.
kh-check-ew2 = topology.ebs.csi.aws.com/zone=eu-west-2a
Then I put a nodeSelector in the podSpec of the khcheck object based on the same for the nodes.
The main pod has the nodeSelector but the init/check pod don't pick up that value and therefore go into different AZ's and cannot mount the volume.
Is there anyway to get them to use the nodeSelector labels ?
Many thanks.
The text was updated successfully, but these errors were encountered: