openshift
operator/v1: Move KubeScheduler CRD to run-level 50
The outgoing level 25 is from openshift/cluster-kube-scheduler-operator@530e585f63 (openshift/cluster-kube-scheduler-operator#118). But while it makes sense to want a scheduler early so that later pods can get scheduled, cluster bootstrapping and other outgoing clusters already have a scheduler in place. For example, you need a functional scheduler, Deployment controller, and ReplicaSet controller to roll out the scheduler operator. By consolidating in the highly-parallel default level 50, we allow for some time savings (especially once we shift kube-controller-manager-operator from 25 to 50 as well, which I plan on doing next).
Hello @wking! Some important instructions when contributing to openshift/api: API design plays an important part in the user experience of OpenShift and as such API PRs are subject to a high level of scrutiny to ensure they follow our best practices. If you haven't already done so, please review the OpenShift API Conventions and ensure that your proposed changes are compliant. Following these conventions will help expedite the api review process for your PR.
![openshift-ci[bot] avatar](https://avatars.githubusercontent.com/in/91280?v=4 "Published by a pub.dev verified publisher"){kind=small}
Scheduler should install and update before any other component so that new scheduling techniques can be used.
/hold
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: deads2k, wking
The full list of commands accepted by this bot can be found here.
The pull request process is described here
- ~~OWNERS~~ [deads2k]
Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment
@wking: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/integration | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test integration |
| ci/prow/verify-crd-schema | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test verify-crd-schema |
| ci/prow/e2e-aws-serial-techpreview | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test e2e-aws-serial-techpreview |
| ci/prow/e2e-upgrade-minor | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test e2e-upgrade-minor |
Full PR test history. Your PR dashboard.
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.
Issues go stale after 90d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
Exclude this issue from closing by commenting /lifecycle frozen.
If this issue is safe to close now please do so with /close.
/lifecycle rotten /remove-lifecycle stale
@wking: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:
| Test name | Commit | Details | Required | Rerun command |
|---|---|---|---|---|
| ci/prow/integration | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test integration |
| ci/prow/verify-crd-schema | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test verify-crd-schema |
| ci/prow/e2e-aws-serial-techpreview | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test e2e-aws-serial-techpreview |
| ci/prow/e2e-aws-ovn-techpreview | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test e2e-aws-ovn-techpreview |
| ci/prow/e2e-upgrade-minor | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test e2e-upgrade-minor |
| ci/prow/e2e-aws-ovn | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test e2e-aws-ovn |
| ci/prow/e2e-aws-ovn-hypershift | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test e2e-aws-ovn-hypershift |
| ci/prow/e2e-upgrade | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test e2e-upgrade |
| ci/prow/e2e-aws-serial | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test e2e-aws-serial |
| ci/prow/minor-e2e-upgrade-minor | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test minor-e2e-upgrade-minor |
| ci/prow/minor-images | d8fbe5b5c60ea095b5ab48a1f0ecd37efb0bb652 | link | true | /test minor-images |
Full PR test history. Your PR dashboard.
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-sigs/prow repository. I understand the commands that are listed here.
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting /reopen.
Mark the issue as fresh by commenting /remove-lifecycle rotten.
Exclude this issue from closing again by commenting /lifecycle frozen.
/close
@openshift-bot: Closed this PR.
In response to this:
Rotten issues close after 30d of inactivity.
Reopen the issue by commenting
/reopen. Mark the issue as fresh by commenting/remove-lifecycle rotten. Exclude this issue from closing again by commenting/lifecycle frozen./close
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-sigs/prow repository.