NE-1476: Allow test pods to access DNS metrics ports #30753
Conversation
|
Pipeline controller notification For optional jobs, comment This repository is configured in: automatic mode |
openshift-ci-robot
added
the
jira/valid-reference
|
@rfredette: This pull request references NE-1476 which is a valid jira issue. DetailsIn response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: rfredette The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Scheduling required tests: |
|
/retest |
rfredette
force-pushed
the
NE-1476-dns-networkpolicies
branch
from
d023e22 to
a8e8ab9
Compare
|
Scheduling required tests: |
New default network policies will limit access to DNS and DNS operator metrics ports to only pods in the openshift-monitoring namespace. Rather than creating test pods in the openshift-monitoring namespace, add a network policy that allows access to these metrics ports from the test namespace.
rfredette
force-pushed
the
NE-1476-dns-networkpolicies
branch
from
a8e8ab9 to
545fbde
Compare
|
Scheduling required tests: |
3 participants
New default network policies will limit access to DNS and DNS operator metrics ports to only pods in the openshift-monitoring namespace. Rather than creating test pods in the openshift-monitoring namespace, add network policies that allow access to these metrics ports from the test namespace.