Changes in the private subnet consideration

[badaldavda8]

This is because for internal ELB auto subnet discovery, both tags are used -
kubernetes.io/role/internal-elb 1
kubernetes.io/cluster/ shared

Since as per code, first kubernetes.io/cluster/ is checked and then kubernetes.io/role/internal-elb is checked.

If kubernetes.io/cluster/ is not mentioned, then internal ELB is created on Public Subnets.
kubernetes/kubernetes#29298 (comment)

Issue #, if available:

Description of changes:

By submitting this pull request, I confirm that you can use, modify, copy, and redistribute this contribution, under the terms of your choice.

[M00nF1sh]

Hi,
I suggest move the "Private Subnet Tagging Requirement for Internal Load Balancers" as a level 3 header under "Subnet Tagging Requirement" instead. Since the "kubernetes.io/cluster/" is already expressed in "Subnet Tagging Requirement".
Also, we can add "Public Subnet Tagging"(kubernetes.io/role/elb) as a sub-item under "Subnet Tagging Requirement" as well.

[nrdlngr]

@M00nF1sh, I agree with your suggestion. I think the public/private considerations should fall under the subnet requirements, since the cluster tag is required for ALL subnets.

[nrdlngr]

@badaldavda8, thanks for your interest in improving our documentation. I've opted instead to move the load balancer requirements under the subnet tag section, and I've made it more obvious that the cluster tag should apply to all subnets.