-
Notifications
You must be signed in to change notification settings - Fork 4.7k
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
OCPBUGS-43777: apiserver: add tests to verify kube-apiserver is accessible via different endpoints #29339
base: master
Are you sure you want to change the base?
Conversation
@vrutkovs: This pull request references Jira Issue OCPBUGS-43777, which is valid. 3 validation(s) were run on this bug
Requesting review from QA contact: 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. |
24188fa
to
6252a14
Compare
/retest |
Job Failure Risk Analysis for sha: 6252a14
|
test/extended/apiserver/access.go
Outdated
} else { | ||
apiPath = strings.Replace(externalAPIUrl.Host, "api.", "api-int.", 1) | ||
} |
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 api-int.*
always going to resolve to the internal API server endpoint?
Would pulling the internal API server URL using infra.Status.APIServerInternalURL
be more reflective of the flow that a user/client may attempt to take if they were to look at the Infrastructure
API?
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.
Yes, good point. iiuc Hypershift may use a different URL for internal URL
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.
Fixed in e1fd7a8
6252a14
to
e1fd7a8
Compare
Job Failure Risk Analysis for sha: e1fd7a8
|
e1fd7a8
to
c030cf7
Compare
Job Failure Risk Analysis for sha: c030cf7
|
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.
Changes look reasonable to me.
/lgtm
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: everettraven, vrutkovs 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 |
Add tests which check that kube-apiserver is reachable via service network, external and internal api endpoints
c030cf7
to
587d445
Compare
New changes are detected. LGTM label has been removed. |
@vrutkovs: 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. |
Job Failure Risk Analysis for sha: 587d445
|
Add tests which check that kube-apiserver is reachable via service network, external and internal api endpoints
TODO:
kube-apiserver should be accessible via service network endpoint
failing in pull-ci-openshift-origin-master-e2e-metal-ipi-ovn-ipv6