Bug 1762618: pkg/asset/ignition: bootstrap kubeconfig to use api-int #2647
Conversation
|
@jstuever: This pull request references Bugzilla bug 1762618, which is valid. The bug has been moved to the POST state. 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 kubernetes/test-infra repository. |
openshift-ci-robot
added
bugzilla/valid-bug
Prior to this change, the default kubeconfig on the bootstrap host used the external api url. This caused issues when the external api was not available such as when proxy is configured but the noProxy list does not contain the external api. In such situation, the bootstrap host fails to report bootstrap complete to the cluster. As a result, the installer fails during the wait-for bootstrap-complete stage. This change adds a new kubeconfig (adminInternal) which points to api-int. The bootstrap host defaults to this new kubeconfig. Api-int is already in the noProxy list. As a result, the bootstrap host can report complete even when the external api is inaccessible.
|
/retest |
|
/test e2e-gcp |
|
/test e2e-azure |
|
/approve |
openshift-ci-robot
added
the
approved
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, jstuever, patrickdillon 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 |
|
/retest |
|
@jstuever: All pull requests linked via external trackers have merged. Bugzilla bug 1762618 has been moved to the MODIFIED state. 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 kubernetes/test-infra repository. |
|
@jstuever: The following test failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. 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. |
Prior to this change, the default kubeconfig on the bootstrap host used
the external api url. This caused issues when the external api was not
available such as when proxy is configured but the noProxy list does not
contain the external api. In such situation, the bootstrap host fails to
report bootstrap complete to the cluster. As a result, the installer
fails during the wait-for bootstrap-complete stage.
This change adds a new kubeconfig (adminInternal) which points to
api-int. The bootstrap host defaults to this new kubeconfig. Api-int
is already in the noProxy list. As a result, the bootstrap host can
report complete even when the external api is inaccessible.