Skip to content
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

SDN-4952:Add new parameter namespaces-for-inter-network-service-access #2604

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

Conversation

ricky-rav
Copy link
Contributor

New config parameter namespaces-for-inter-network-service-access holds a list of namespaces to which ovn kubernetes will allow access to cluster IP services that are in UDNs.

Depends on an OVNK PR (work in progress)

New config parameter namespaces-for-inter-network-service-access holds a list of namespaces to which ovn kubernetes will allow access to cluster IP services that are in UDNs.

Signed-off-by: Riccardo Ravaioli <[email protected]>
@openshift-ci-robot
Copy link
Contributor

openshift-ci-robot commented Dec 13, 2024

@ricky-rav: This pull request references SDN-4952 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:

New config parameter namespaces-for-inter-network-service-access holds a list of namespaces to which ovn kubernetes will allow access to cluster IP services that are in UDNs.

Depends on an OVNK PR (work in progress)

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 openshift-ci-robot added the jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. label Dec 13, 2024
Copy link
Contributor

openshift-ci bot commented Dec 13, 2024

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ricky-rav
Once this PR has been reviewed and has the lgtm label, please assign jcaamano for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found 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

Copy link
Contributor

openshift-ci bot commented Dec 13, 2024

@ricky-rav: 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/okd-scos-e2e-aws-ovn 960dda5 link false /test okd-scos-e2e-aws-ovn
ci/prow/security 960dda5 link false /test security
ci/prow/e2e-metal-ipi-ovn-ipv6-ipsec 960dda5 link false /test e2e-metal-ipi-ovn-ipv6-ipsec
ci/prow/e2e-aws-ovn-single-node 960dda5 link false /test e2e-aws-ovn-single-node
ci/prow/4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade 960dda5 link false /test 4.18-upgrade-from-stable-4.17-e2e-azure-ovn-upgrade
ci/prow/e2e-vsphere-ovn-dualstack-primaryv6 960dda5 link false /test e2e-vsphere-ovn-dualstack-primaryv6
ci/prow/e2e-gcp-ovn-techpreview 960dda5 link true /test e2e-gcp-ovn-techpreview
ci/prow/e2e-aws-hypershift-ovn-kubevirt 960dda5 link false /test e2e-aws-hypershift-ovn-kubevirt
ci/prow/e2e-aws-ovn-serial 960dda5 link false /test e2e-aws-ovn-serial

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
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.

2 participants