search

openshift / cluster-operator

52 stars 35 forks source link

WIP: Run master install whenever new machines need it #257

Closed csrwng closed 6 years ago

csrwng commented 6 years ago

The master controller now generates an inventory based on which machines are available at the time the controller runs. It uses the Status.Versions.ControlPlane field to keep track of which Machines have had the master job run on them.

csrwng commented 6 years ago

comments addressed, rebasing

openshift-bot commented 6 years ago

@csrwng: PR needs rebase.

Instructions for interacting with me using PR comments are available [here](https://git.k8s.io/community/contributors/guide/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository.
openshift-ci-robot commented 6 years ago

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

Test name Commit Details Rerun command
ci/openshift-jenkins/unit 676176802dc7d2b226644b0b9ef78e1b651bce45 link /test unit

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](https://git.k8s.io/community/contributors/devel/pull-requests.md). If you have questions or suggestions related to my behavior, please file an issue against the [kubernetes/test-infra](https://github.com/kubernetes/test-infra/issues/new?title=Prow%20issue:) repository. I understand the commands that are listed [here](https://go.k8s.io/bot-commands).
csrwng commented 6 years ago

Closing this as the master will need to manage its own nodes in the 4.0 setup.