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
There are two option to prevent from posible node affinity conflict during controllers restarts when using EBS volumens: make topology aware volume to the same AZs, or designing Autoscaling Groups following what is explained in the AWS article Creating Kubernetes Auto Scaling Groups for Multiple Availability Zones (one ASG per AZ for EBS volume and one single ASG per Multiple AZ for EFS volumes). At the moment of publishing this blueprints, terraform-aws-modules/eks/aws does not support availability_zones atribute for the embedded aws_autoscaling_group resource, then the first option is applied in g3 Storage Class.
Only with setting g3 topology Storage Class is not enough. It is required to assigned Pod to 1 AZ only
The text was updated successfully, but these errors were encountered:
There are two option to prevent from posible
node affinity conflict
during controllers restarts when using EBS volumens: make topology aware volume to the same AZs, or designing Autoscaling Groups following what is explained in the AWS article Creating Kubernetes Auto Scaling Groups for Multiple Availability Zones (one ASG per AZ for EBS volume and one single ASG per Multiple AZ for EFS volumes). At the moment of publishing this blueprints,terraform-aws-modules/eks/aws
does not supportavailability_zones
atribute for the embeddedaws_autoscaling_group
resource, then the first option is applied ing3
Storage Class.Only with setting
g3
topology Storage Class is not enough. It is required to assigned Pod to 1 AZ onlyThe text was updated successfully, but these errors were encountered: