This repository has been archived by the owner on Jun 29, 2022. It is now read-only.
aws-ebs-csi-driver: add NetworkPolicy allowing access to metadata #865
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
After we created aws-ebs-csi-driver component, we added a patch to Lokomotive, which deploys a Global Network Policy, which blocks access to EC2 Instance Metadata by default for all pods, which ended up breaking the component functionality. The issue was not spotted before, as the component does not have readiness probes defined, which has been reported upstream: kubernetes-sigs/aws-ebs-csi-driver#548 This commit fixes the component functionality, by adding the NetworkPolicy object selecting the controller pods, which unblocks all egress traffic for it, which bypasses the Global Network Policy. Closes #864 Signed-off-by: Mateusz Gozdek <mateusz@kinvolk.io>
surajssd
approved these changes
Aug 27, 2020
knrt10
approved these changes
Aug 27, 2020
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
After we created aws-ebs-csi-driver component, we added a patch to
Lokomotive, which deploys a Global Network Policy, which blocks access
to EC2 Instance Metadata by default for all pods, which ended up
breaking the component functionality.
The issue was not spotted before, as the component does not have
readiness probes defined, which has been reported upstream:
kubernetes-sigs/aws-ebs-csi-driver#548
This commit fixes the component functionality, by adding the
NetworkPolicy object selecting the controller pods, which unblocks all
egress traffic for it, which bypasses the Global Network Policy.
Closes #864
Signed-off-by: Mateusz Gozdek mateusz@kinvolk.io