-
Notifications
You must be signed in to change notification settings - Fork 380
OCPBUGS-61088: create networkpolicy settings for in-cluster monitoring #2656
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
/retitle [WIP] OCPBUGS-61088: create networkpolicy settings for in-cluster monitoring |
@juzhao: This pull request references Jira Issue OCPBUGS-61088, which is invalid:
Comment The bug has been updated to refer to the pull request using the external bug tracker. In 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. |
/jira refresh |
@juzhao: This pull request references Jira Issue OCPBUGS-61088, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: In 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. |
@openshift-ci-robot: GitHub didn't allow me to request PR reviews from the following users: juzhao. Note that only openshift members and repo collaborators can review this PR, and authors cannot review their own PRs. In 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 kubernetes-sigs/prow repository. |
], | ||
}, | ||
], | ||
egress: [ |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is there any recommendation to allow egress traffic only to the API service? This is the only destination which ksm should try to connect but I guess that it's not trivial to accommodate classic OCP (self-managed) and hosted clusters (HyperShift).
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
networkpolicy applied to pod only, seems we can not define for API service, will check again.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
we can use pod/namespace selectors in rgress rules https://kubernetes.io/docs/concepts/services-networking/network-policies/#behavior-of-to-and-from-selectors
but yes, it could be tricky to have it right for all the flavors.
maybe we can create a ticket for this, and try to narrow down egress for ksm and others in a follow up PR, with some manual/payload testing we should be able to get it right. (maybe in 4.21)
/retest |
/test verify |
/retest |
/retest |
/retest |
1 similar comment
/retest |
go-proxy CI issues are unrelated to the patch |
e2e CI error is
seems prow issue |
/retest |
/retest-required |
same issue as #2681 (comment)
|
tested with PR, no regression issues. |
@juzhao: This PR has been marked as verified by In 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. |
/test e2e-aws-ovn-techpreview |
/test e2e-agnostic-operator |
1 similar comment
/test e2e-agnostic-operator |
/retest-required |
/retest |
@juzhao: The following tests failed, say
Full PR test history. Your PR dashboard. 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 kubernetes-sigs/prow repository. I understand the commands that are listed here. |
see https://issues.redhat.com/browse/OCPBUGS-61088, use this bug to set networkpolicy for in-cluster monitoring
this PR replaced #2645, 2645 does not include networkpolicy settings for alertmanager/prometheus/thanos-querier, since there is default deny network settings for all monitoring pods, if we don't include them, CI jobs would be failed for them