Fill random available zones if no subnet availability zone is provided in the Subnet resource about provider-aws

[vadasambar]

@hasheddan yes! We should let availabilityZone be optional and allow AWS to pick one for us if no availability zone is specified.

[hasheddan]

@vadasambar Great! When the EKSCluster resource is moved to v1beta1 this should be the experienced behavior because it most closely reflects the AWS API. I will keep this issue open to denote this specific desired behavior. v1beta1 migration is loosely tracked by #24 but there will likely be another more focused issue opened when the work is being started. Thank you for raising this!

[hasheddan]

@vadasambar thanks for raising this issue to improve user experience :) I believe the availabilityZone field is currently required on Subnet resources. The AWS API states that they will select one for you if the field is not defined on creation. Are you suggesting that we make the availabilityZone field optional, and then late initialize it if a value is not provided and AWS picks one?

[muvaf]

@hasheddan is this still relevant?

[haarchri]

@hasheddan @muvaf think we can close this Issue ?