docs/user/overview: OpenShift-specific components before bootstrap control-plane teardown#2475
Conversation
…ntrol-plane teardown Since 82d81d9 (data/data/bootstrap: use loopback kubeconfig for API access, 2019-07-24, openshift#2086), we've been pushing the OpenShift-specific components via a loopback kubeconfig and the bootstrap control plane. Since 108a45b (data/bootstrap: Replace openshift.sh with cluster-bootstrap, 2019-01-24, landed 2019-09-30, openshift#1381), that push has always happened before the bootstrap control plane shuts down. I've changed "into" to "via" because the data passes through either control plane on its way to rest in the shared etcd cluster. I've dropped "then" from the final step because none of the other steps said "then". I think ordering is clear enough from our use of an ordered list ;).
openshift-ci-robot
added
size/XS
|
CC @kalexand-rh, since this will need an upstream port to openshift-docs' 4.2 branch once it lands here. |
|
/approve |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: abhinavdahiya, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/retest Please review the full test history for this PR and help us cut down flakes. |
|
@wking: 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. 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/test-infra repository. I understand the commands that are listed here. |
5 participants
Since 82d81d9 (#2086), we've been pushing the OpenShift-specific components via a loopback kubeconfig and the bootstrap control plane. Since 108a45b (#1381), that push has always happened before the bootstrap control plane shuts down.
I've changed "into" to "via" because the data passes through either control plane on its way to rest in the shared etcd cluster.
I've dropped "then" from the final step because none of the other steps said "then". I think ordering is clear enough from our use of an ordered list ;).