Skip to content

Conversation

@smarterclayton
Copy link
Contributor

@smarterclayton smarterclayton commented Oct 16, 2018

Perform bootstrapping in the background when client cert rotation is on,
enabling static pods to start before a control plane is reachable.

Argument that we enable this in master now for testing and to allow the installer to start consuming it. We then backport it to 1.12 when the rebase lands.

@openshift-ci-robot openshift-ci-robot added do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. size/L Denotes a PR that changes 100-499 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Oct 16, 2018
@bparees bparees removed their request for review October 16, 2018 20:21
@smarterclayton
Copy link
Contributor Author

/retest

@openshift-ci-robot openshift-ci-robot added size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. and removed size/L Denotes a PR that changes 100-499 lines, ignoring generated files. labels Oct 17, 2018
@smarterclayton
Copy link
Contributor Author

/retest

Perform bootstrapping in the background when client cert rotation is on,
enabling static pods to start before a control plane is reachable.
@openshift-ci-robot openshift-ci-robot added size/L Denotes a PR that changes 100-499 lines, ignoring generated files. and removed size/XL Denotes a PR that changes 500-999 lines, ignoring generated files. labels Oct 23, 2018
@smarterclayton
Copy link
Contributor Author

/retest

@smarterclayton
Copy link
Contributor Author

/skip
/retest

@smarterclayton
Copy link
Contributor Author

/test launch-gcp

@smarterclayton
Copy link
Contributor Author

/test e2e-gcp-launch

@smarterclayton
Copy link
Contributor Author

@aaronlevy @crawford @deads2k @sjenning this has been tested manually pretty well. since we haven't rebased to 1.12 yet, we could merge this and then update the installer - allowing us to use static pods even if bootstrapping while the master is down (I tested on a one node master cluster). the delta for a 1.12 backports is pretty small, so it's a low risk carry for us to develop against while we finish out the upstream. At worst, we just get extra testing. So I'd probably say we should merge even assuming it changes some upstream, assume that we can carry it throughout 4.0 if necessary, and then hopefully have it in 1.13.

/retest

@crawford
Copy link
Contributor

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Oct 25, 2018
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: crawford, smarterclayton

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Details 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

@smarterclayton
Copy link
Contributor Author

Leaving this under the hold until I sync with David in the morning.

Were we blocked on moving etcd to static pod on this? Or were there other things in the way of that?

@smarterclayton smarterclayton changed the title WIP: UPSTREAM: 69890: Bootstrap in background WIP: UPSTREAM: 69890: Run static pods before bootstrap Oct 25, 2018
@crawford
Copy link
Contributor

Were we blocked on moving etcd to static pod on this? Or were there other things in the way of that?

My understanding was that this was the only thing in the way.

@smarterclayton
Copy link
Contributor Author

David agreed verbally, merging.

@smarterclayton smarterclayton removed the do-not-merge/work-in-progress Indicates that a PR should not merge because it is a work in progress. label Oct 25, 2018
@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

5 similar comments
@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@deads2k
Copy link
Contributor

deads2k commented Oct 26, 2018

@aaronlevy @crawford @deads2k @sjenning this has been tested manually pretty well. since we haven't rebased to 1.12 yet, we could merge this and then update the installer - allowing us to use static pods even if bootstrapping while the master is down (I tested on a one node master cluster). the delta for a 1.12 backports is pretty small, so it's a low risk carry for us to develop against while we finish out the upstream. At worst, we just get extra testing. So I'd probably say we should merge even assuming it changes some upstream, assume that we can carry it throughout 4.0 if necessary, and then hopefully have it in 1.13.

Yeah, it makes sense for us to do this.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

1 similar comment
@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@smarterclayton
Copy link
Contributor Author

/retest

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

4 similar comments
@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@smarterclayton
Copy link
Contributor Author

Crio is super flaky. I’m going to spawn issues for it, but for now I’m going to merge to unblock static pods

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

6 similar comments
@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@smarterclayton
Copy link
Contributor Author

/retest

@openshift-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-ci-robot
Copy link

openshift-ci-robot commented Oct 28, 2018

@smarterclayton: The following test failed, say /retest to rerun them all:

Test name Commit Details Rerun command
ci/openshift-jenkins/extended_clusterup 04a9289 link /test extended_clusterup

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.

Details

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-merge-robot
Copy link
Contributor

/retest

Please review the full test history for this PR and help us cut down flakes.

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. lgtm Indicates that a PR is ready to be merged. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants