-
Notifications
You must be signed in to change notification settings - Fork 295
Suggestion: Validate if existing subnets have appropriate tags added #779
Comments
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. |
@redbaron Good point 👍 |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Stale issues rot after 30d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
Rotten issues close after 30d of inactivity. Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
@fejta-bot: Closing this issue. In response to this:
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. |
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
The text was updated successfully, but these errors were encountered: