-
Notifications
You must be signed in to change notification settings - Fork 1.5k
OCPBUGS-54901: Check for API server reachability before updating kubeconfig #10099
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
base: main
Are you sure you want to change the base?
Conversation
|
@sadasu: This pull request references Jira Issue OCPBUGS-54901, which is valid. The bug has been moved to the POST state. 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. DetailsIn 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. |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
40a7a2a to
a52db9f
Compare
|
/test e2e-gcp-custom-dns |
a52db9f to
15d12bc
Compare
|
/test e2e-gcp-custom-dns |
29c8659 to
7870a9b
Compare
|
/test e2e-gcp-custom-dns |
7870a9b to
66ed7a0
Compare
|
/test e2e-gcp-custom-dns |
66ed7a0 to
ef102d4
Compare
|
/test e2e-gcp-custom-dns |
ef102d4 to
ed825e8
Compare
|
/test e2e-gcp-custom-dns |
ed825e8 to
11d25b6
Compare
|
/test e2e-gcp-custom-dns |
11d25b6 to
e956037
Compare
|
/test e2e-gcp-custom-dns |
|
/cc |
|
/test e2e-gcp-ovn |
1 similar comment
|
/test e2e-gcp-ovn |
e956037 to
357d22c
Compare
|
/test e2e-gcp-custom-dns |
|
/test e2e-gcp-ovn |
|
@sadasu: The following tests failed, say
Full PR test history. Your PR dashboard. DetailsInstructions 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. |
When private clusters are installed with userProvisionedDNS enabled, it is likely that the install host is not in the same network as the cluster and the LB IP is not reachable from the install host. Using a kubeconfig with Dialer context does not help with accessing the cluster. So, continue using the originial kubeconfig with the expectation that a proxy / bastion host has been setup to access the cluster via its API server URL.
357d22c to
18e4cf3
Compare
Only applicable for custom-dns