fix(eks): KubectlProvider
creates un-necessary security group
#13178
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.
Following #10200, our
KubectlProvider
functions are now provisioned inside a VPC when applicable. A somewhat unintended side effect is that the provider framework will create and use a dedicated security group for its functions.This can violate organizational policies that don't allow CDK to create security groups. We can easily avoid this by simply reusing the
kubectlSecurityGroup
, which must be defined in this case, and passing it to the provider.Fixes #12952
By submitting this pull request, I confirm that my contribution is made under the terms of the Apache-2.0 license