OCPBUGS-4294: bootstrap-kube-scheduler: specify resources.requests

[knelasevero]

Backporting #445

[openshift-ci]

@knelasevero: No Bugzilla bug is referenced in the title of this pull request.
To reference a bug, add 'Bug XXX:' to the title of this pull request and request another bug refresh with /bugzilla refresh.

In response to this:

OCPBUGS-4294: bootstrap-kube-scheduler: specify resources.requests

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]

@knelasevero: This pull request references Jira Issue OCPBUGS-4294, which is invalid:

• expected the bug to target the "4.11.z" version, but it targets "4.11.0" instead
• expected dependent Jira Issue OCPBUGS-4293 to target a version in 4.12.0, but it targets "4.13.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Backporting #445

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.

[knelasevero]

/jira refresh

[openshift-ci-robot]

@knelasevero: This pull request references Jira Issue OCPBUGS-4294, which is invalid:

• expected dependent Jira Issue OCPBUGS-4293 to target a version in 4.12.0, but it targets "4.13.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[knelasevero]

/jira refresh

[openshift-ci-robot]

@knelasevero: This pull request references Jira Issue OCPBUGS-4294, which is invalid:

• expected dependent Jira Issue OCPBUGS-4293 to target a version in 4.12.0, but it targets "4.13.0" instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[knelasevero]

/jira refresh

[openshift-ci-robot]

@knelasevero: This pull request references Jira Issue OCPBUGS-4294, which is invalid:

• expected dependent Jira Issue OCPBUGS-4292 to be in one of the following states: VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE), but it is POST instead

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

/jira refresh

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.

[ingvagabund]

/lgtm

[ingvagabund]

/label backport-risk-assessed

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: ingvagabund, knelasevero

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:

• OWNERS [ingvagabund]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[openshift-ci]

@knelasevero: all tests passed!

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.

[kasturinarra]

/label cherry-pick-approved

[ingvagabund]

/jira refresh

[openshift-ci-robot]

@ingvagabund: This pull request references Jira Issue OCPBUGS-4294, which is valid. The bug has been moved to the POST state.

6 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target version (4.11.z) matches configured target version for branch (4.11.z)
• bug is in the state New, which is one of the valid states (NEW, ASSIGNED, POST)
• dependent bug Jira Issue OCPBUGS-4292 is in the state Verified, which is one of the valid states (VERIFIED, RELEASE PENDING, CLOSED (ERRATA), CLOSED (CURRENT RELEASE), CLOSED (DONE))
• dependent Jira Issue OCPBUGS-4292 targets the "4.12.0" version, which is one of the valid target versions: 4.12.0
• bug has dependents

Requesting review from QA contact:
/cc @kasturinarra

In response to this:

/jira refresh

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]

@knelasevero: All pull requests linked via external trackers have merged:

• openshift/cluster-kube-scheduler-operator#449

Jira Issue OCPBUGS-4294 has been moved to the MODIFIED state.

In response to this:

Backporting #445

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.