Suggestion: Validate if existing subnets have appropriate tags added

[mumoshu]

As required by K8S, and emit validation errors accordingly so that users can notice what action(s) are required in order to deploy a kube-aws cluster into existing subnet(s).

Ref #52 (comment)

cc @redbaron @c-knowles @danielfm @camilb

[redbaron]

It can't be an error as tags are not mandatory for cluster to function. lets say if service type LoadBalancer is never used, then no tags is needed. It can be a warning at best.

[mumoshu]

@redbaron Good point 👍
I was under the impression that we'd want to enable type: LoadBalancer services even for a cluster deployed into existing subnet(s) but yes, the service type isn't addressed even in the K8S conformance test hence it can not be said as a "requirement" of a K8S cluster.
A warning would be nice.

[fejta-bot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle stale

[fejta-bot]

Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.

If this issue is safe to close now please do so with /close.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/lifecycle rotten

[fejta-bot]

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

[k8s-ci-robot]

@fejta-bot: Closing this issue.

In response to this:

Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.

Send feedback to sig-testing, kubernetes/test-infra and/or fejta.
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.