refactor: Updates to privatelink-access based on latest working pattern #2065
+50
−40
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.
Description
We have used the
privatelink-access
pattern internally and it mostly worked all good. In this PR included are some minor updates that we had to do to make it work:Motivation and Context
We needed to follow this pattern to connect two VPCs in different accounts and one was hosting an EKS cluster. Contributing back changes that we had to make in order to make the pattern work.
How was this change tested?
pre-commit run -a
with this PRAdditional Notes
N/A