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

UPSTREAM: 113799: tests: network: Prefer internal IPs first #1446

Merged
merged 1 commit into from
Feb 21, 2023

Conversation

jluhrsen
Copy link

Many clusters block direct requests from internal resources to the nodes external IPs as best practice. All accesses from internal resources that want to access resources running on nodes go through load balancers, nodes being on private or public subnets. Let's prefer internal IPs first, so the tests can work even when there are security group rules present blocking requests to the external IPs.

We should not require ExternalIP for Conformance, but should keep testing ExternalIPs in sig network.

Signed-off-by: Rafael Fonseca r4f4rfs@gmail.com

What type of PR is this?

What this PR does / why we need it:

Which issue(s) this PR fixes:

Fixes #

Special notes for your reviewer:

Does this PR introduce a user-facing change?


Additional documentation e.g., KEPs (Kubernetes Enhancement Proposals), usage docs, etc.:


@openshift-ci-robot openshift-ci-robot added the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Dec 21, 2022
@jluhrsen
Copy link
Author

/kind bug

@openshift-ci-robot
Copy link

@jluhrsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Dec 21, 2022
@openshift-ci openshift-ci bot requested review from deads2k and sttts December 21, 2022 21:46
@openshift-ci-robot
Copy link

@jluhrsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@jluhrsen
Copy link
Author

/retest

1 similar comment
@jluhrsen
Copy link
Author

jluhrsen commented Jan 3, 2023

/retest

@jluhrsen jluhrsen changed the title UPSTRAM: <carry>: tests: network: Prefer internal IPs first UPSTREAM: <carry>: tests: network: Prefer internal IPs first Jan 3, 2023
@jluhrsen
Copy link
Author

jluhrsen commented Jan 3, 2023

@deads2k, when you have a chance can you take a look at this one please?

@jluhrsen
Copy link
Author

jluhrsen commented Jan 4, 2023

/retest

@jluhrsen
Copy link
Author

jluhrsen commented Jan 4, 2023

/validate-backports

@openshift-ci-robot
Copy link

@jluhrsen: the contents of this pull request could not be automatically validated.

The following commits could not be validated and must be approved by a top-level approver:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

Many clusters block direct requests from internal resources to the nodes
external IPs as best practice. All accesses from internal resources that
want to access resources running on nodes go through load balancers,
nodes being on private or public subnets. Let's prefer internal IPs
first, so the tests can work even when there are security group rules
present blocking requests to the external IPs.

We should not require ExternalIP for Conformance, but should keep
testing ExternalIPs in sig network.

Signed-off-by: Rafael Fonseca <r4f4rfs@gmail.com>
@openshift-ci-robot openshift-ci-robot added the backports/validated-commits Indicates that all commits come to merged upstream PRs. label Jan 4, 2023
@openshift-ci-robot
Copy link

@jluhrsen: the contents of this pull request could be automatically validated.

The following commits are valid:

Comment /validate-backports to re-evaluate validity of the upstream PRs, for example when they are merged upstream.

@openshift-ci-robot openshift-ci-robot removed the backports/unvalidated-commits Indicates that not all commits come to merged upstream PRs. label Jan 4, 2023
@jluhrsen jluhrsen changed the title UPSTREAM: <carry>: tests: network: Prefer internal IPs first UPSTREAM: 113799: tests: network: Prefer internal IPs first Jan 4, 2023
Copy link

@soltysh soltysh left a comment

Choose a reason for hiding this comment

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

/lgtm
/approve

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Feb 8, 2023
@openshift-ci
Copy link

openshift-ci bot commented Feb 8, 2023

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jluhrsen, soltysh

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 Feb 8, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 149fe52 and 2 for PR HEAD 25af2bb in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD c729678 and 1 for PR HEAD 25af2bb in total

@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 919a59b and 0 for PR HEAD 25af2bb in total

@openshift-ci
Copy link

openshift-ci bot commented Feb 16, 2023

@jluhrsen: 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-csi 25af2bb link false /test e2e-aws-csi
ci/prow/4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade 25af2bb link false /test 4.11-upgrade-from-stable-4.10-e2e-aws-ovn-upgrade

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/test-infra repository. I understand the commands that are listed here.

@openshift-ci-robot
Copy link

/hold

Revision 25af2bb was retested 3 times: holding

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 16, 2023
@jluhrsen
Copy link
Author

/retest-required
/hold cancel

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Feb 20, 2023
@openshift-ci-robot
Copy link

/retest-required

Remaining retests: 0 against base HEAD 8564fb8 and 2 for PR HEAD 25af2bb in total

@jluhrsen
Copy link
Author

/retest-required

@openshift-merge-robot openshift-merge-robot merged commit 518f3ed into openshift:master Feb 21, 2023
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. backports/validated-commits Indicates that all commits come to merged upstream PRs. kind/bug Categorizes issue or PR as related to a bug. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants