Skip to content

WiP: PSAP-1178: Add NetworkPolicy k8s resources #1323

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

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

jmencak
Copy link
Contributor

@jmencak jmencak commented Apr 16, 2025

This change adds a default deny NetworkPolicy for ingress and egress in the openshift-cluster-node-tuning-operator namespace. The following flows are allowed by NetworkPolicies:

  • access to the API server
  • access to NTO Metrics server
  • access to NTO Webhook server

Resolves: PSAP-1178

@openshift-ci-robot openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Apr 16, 2025
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Apr 16, 2025

@jmencak: This pull request references PSAP-1178 which is a valid jira issue.

Warning: The referenced jira issue has an invalid target version for the target branch this PR targets: expected the story to target the "4.19.0" version, but no target version was set.

In response to this:

This change adds a default deny NetworkPolicy for ingress and egress in the openshift-cluster-node-tuning-operator namespace. The following flows are allowed by NetworkPolicies:

  • access to the API server
  • access to NTO Metrics server
  • access to NTO Webhook server

Resolves: PSAP-1178

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 openshift-ci bot added the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Apr 16, 2025
@openshift-ci openshift-ci bot requested review from swatisehgal and yanirq April 16, 2025 16:24
Copy link
Contributor

openshift-ci bot commented Apr 16, 2025

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jmencak

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci openshift-ci bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Apr 16, 2025
@@ -59,8 +59,7 @@ var _ = ginkgo.Describe("[basic][modules] Node Tuning Operator load kernel modul
gomega.Expect(err).NotTo(gomega.HaveOccurred())

ginkgo.By(fmt.Sprintf("trying to remove the %s module if loaded", moduleName))
_, err = util.ExecCmdInPod(pod, "rmmod", moduleName)
gomega.Expect(err).To(gomega.HaveOccurred())
_, _ = util.ExecCmdInPod(pod, "rmmod", moduleName)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why do we need this change?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch, I'll remove this. This is fixed by #1322

@rbaturov
Copy link
Contributor

@jmencak Thanks for your work Jiri.
The network policies look on point to me.
/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Apr 17, 2025
This change adds a default deny NetworkPolicy for ingress and egress
in the openshift-cluster-node-tuning-operator namespace.  The following
flows are allowed by NetworkPolicies:
  - access to the API server
  - access to NTO Metrics server
  - access to NTO Webhook server

Resolves: PSAP-1178
@jmencak jmencak force-pushed the 4.20-network_policy branch from 343a3f0 to 1b61c36 Compare April 17, 2025 09:16
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Apr 17, 2025
Copy link
Contributor

openshift-ci bot commented Apr 17, 2025

New changes are detected. LGTM label has been removed.

Copy link
Contributor

openshift-ci bot commented Apr 17, 2025

@jmencak: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name Commit Details Required Rerun command
ci/prow/e2e-aws-ovn 1b61c36 link true /test e2e-aws-ovn
ci/prow/e2e-hypershift-pao 1b61c36 link true /test e2e-hypershift-pao
ci/prow/okd-scos-e2e-aws-ovn 1b61c36 link false /test okd-scos-e2e-aws-ovn
ci/prow/e2e-hypershift 1b61c36 link true /test e2e-hypershift
ci/prow/e2e-gcp-pao 1b61c36 link true /test e2e-gcp-pao
ci/prow/e2e-gcp-pao-updating-profile 1b61c36 link true /test e2e-gcp-pao-updating-profile
ci/prow/e2e-gcp-pao-workloadhints 1b61c36 link true /test e2e-gcp-pao-workloadhints
ci/prow/e2e-aws-operator 1b61c36 link true /test e2e-aws-operator
ci/prow/e2e-upgrade 1b61c36 link true /test e2e-upgrade
ci/prow/images 1b61c36 link true /test images
ci/prow/e2e-aws-ovn-techpreview 1b61c36 link true /test e2e-aws-ovn-techpreview

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants