fix(vd): allow ingress from virtualization namespace to importer pods#2356
Open
fl64 wants to merge 1 commit into
Open
fix(vd): allow ingress from virtualization namespace to importer pods#2356fl64 wants to merge 1 commit into
fl64 wants to merge 1 commit into
Conversation
When a namespace has a restrictive NetworkPolicy (e.g. project isolation), the CDI controller from d8-virtualization cannot reach importer pods to fetch progress metrics via HTTP. As a result, DataVolume.Status.Progress stays N/A and VirtualDisk shows no intermediate progress. Add an Ingress rule to the NetworkPolicy created for importer/DVCR pods, allowing incoming traffic from the namespace labeled module=virtualization. This enables the CDI controller to scrape progress metrics from importer pods even in isolated namespaces. Signed-off-by: Pavel Tishkov <[email protected]>
This file contains hidden or 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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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
Allow ingress from virtualization namespace to importer pods
Why do we need it, and what problem does it solve?
When a namespace has a restrictive NetworkPolicy (e.g. project isolation), the CDI controller from d8-virtualization cannot reach importer pods to fetch progress metrics via HTTP. As a result, DataVolume.Status.Progress stays N/A and VirtualDisk shows no intermediate progress.
Add an Ingress rule to the NetworkPolicy created for importer/DVCR pods, allowing incoming traffic from the namespace labeled module=virtualization. This enables the CDI controller to scrape progress metrics from importer pods even in isolated namespaces.
What is the expected result?
Checklist
Changelog entries