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

CORS-3936: Add support for public-only networking #9544

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

Conversation

bear-redhat
Copy link

Add support for public-only networking (i.e., a cluster deployed with managed-VPC while has only public subnets)

Ref: https://issues.redhat.com/browse/CORS-3936
Ref: https://issues.redhat.com/browse/DPTP-4342

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

openshift-ci-robot commented Mar 7, 2025

@bear-redhat: This pull request references CORS-3936 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:

Add support for public-only networking (i.e., a cluster deployed with managed-VPC while has only public subnets)

Ref: https://issues.redhat.com/browse/CORS-3936
Ref: https://issues.redhat.com/browse/DPTP-4342

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 requested review from andfasano and mtulio March 7, 2025 16:11
Copy link
Contributor

openshift-ci bot commented Mar 7, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign bfournie 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 Mar 7, 2025

@bear-redhat: 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 256c3a1 link false /test okd-scos-e2e-aws-ovn
ci/prow/okd-scos-images 256c3a1 link true /test okd-scos-images
ci/prow/e2e-vsphere-ovn-multi-network 256c3a1 link false /test e2e-vsphere-ovn-multi-network
ci/prow/e2e-aws-ovn-edge-zones-manifest-validation 256c3a1 link true /test e2e-aws-ovn-edge-zones-manifest-validation
ci/prow/e2e-aws-ovn-single-node 256c3a1 link false /test e2e-aws-ovn-single-node
ci/prow/e2e-aws-ovn-fips 256c3a1 link false /test e2e-aws-ovn-fips
ci/prow/e2e-aws-ovn-shared-vpc-custom-security-groups 256c3a1 link false /test e2e-aws-ovn-shared-vpc-custom-security-groups
ci/prow/e2e-aws-ovn-edge-zones 256c3a1 link false /test e2e-aws-ovn-edge-zones
ci/prow/aro-unit 256c3a1 link true /test aro-unit
ci/prow/unit 256c3a1 link true /test unit
ci/prow/e2e-aws-default-config 256c3a1 link false /test e2e-aws-default-config
ci/prow/e2e-aws-ovn-shared-vpc-edge-zones 256c3a1 link false /test e2e-aws-ovn-shared-vpc-edge-zones
ci/prow/e2e-aws-ovn-heterogeneous 256c3a1 link false /test e2e-aws-ovn-heterogeneous

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