This repository has been archived by the owner on Sep 30, 2020. It is now read-only.
Issue when kube-aws manages/creates subnets #1598
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Subnets in the controller stack not being referenced against the network stack when being managed by kube-aws. Map subnets back to the looked up set by name. Various additional log messages to debug level. Remove some helper functions on tempCtx types by calling the correct path in the stack templates.