There is a problem with EFS volumes when you have a lot of subnets - they can't be created. Actually by now it can only work if you have a network with only 3 public subnets in the 3 AWS availability zones without any additional subnets.
fixes #2164 , helps #1739
This helps by identifying the public subnets, and creates mount targets only for them, it expects the following:
you have 3 public subnets and N number of additional
there is routing table associated with the 3 public subnets, and separate routing table left as default for any number of other private subnets
private routing table is the main table
Since there is no proper way of setting the subnets used by the volumes, I am proposing this so at least it tries to create the EFS mounts properly when you have a lot of subnets.
There is a problem with EFS volumes when you have a lot of subnets - they can't be created. Actually by now it can only work if you have a network with only 3 public subnets in the 3 AWS availability zones without any additional subnets.
fixes #2164 , helps #1739
This helps by identifying the public subnets, and creates mount targets only for them, it expects the following:
Since there is no proper way of setting the subnets used by the volumes, I am proposing this so at least it tries to create the EFS mounts properly when you have a lot of subnets.