[EKS] Remove requirement for full outbound access for worker nodes to join tge cluster

We are using EKS v8 with Kubernetes 1.14. In our setup the outbound access is restricted or blocked or require details on what destination and port the access is required.

While spinning the new EKS cluster we found that without outbound set to 0.0.0.0/0 enabled the worker nodes would not join the cluster. On discussion with AWS support we were told that for this we need to go back to EKS v3.

Can you provide the list of the external sites which EKS worker nodes are trying to access, we can whitelist them and add to SGs.

As a final solution this requirement should be removed as lot of ebterprises will not open outbound with full access.

The issue names EKS v8, Kubernetes 1.14, worker-node cluster joining, and restricted outbound access, but mentions no repository file or test. Start by determining the destinations and ports required during node registration; done would mean documenting or removing the need for 0.0.0.0/0 access while preserving successful worker-node joins.

Written by the indexing model from the issue text.