Bug 1984608: Set kube-scheduler leader election defaults

[damemi]

This sets default LeaderElection values to better handle API server disruption as recommended in https://github.com/openshift/enhancements/blob/master/CONVENTIONS.md#handling-kube-apiserver-disruption

[damemi]

/cc @soltysh

[openshift-ci]

@damemi: An error was encountered querying GitHub for users with public email (knarra@redhat.com) for bug 1984608 on the Bugzilla server at https://bugzilla.redhat.com. No known errors were detected, please see the full error message for details.

Full error message.

non-200 OK status code: 403 Forbidden body: "{\n \"documentation_url\": \"https://docs.github.com/en/free-pro-team@latest/rest/overview/resources-in-the-rest-api#secondary-rate-limits\",\n \"message\": \"You have exceeded a secondary rate limit. Please wait a few minutes before you try again.\"\n}\n"

Please contact an administrator to resolve this issue, then request a bug refresh with /bugzilla refresh.

In response to this:

Bug 1984608: Set kube-scheduler leader election defaults

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.

[damemi]

/retest

[ingvagabund]

/bugzilla refresh

[openshift-ci]

@ingvagabund: This pull request references Bugzilla bug 1984608, which is valid.

3 validation(s) were run on this bug

• bug is open, matching expected state (open)
• bug target release (4.9.0) matches configured target release for branch (4.9.0)
• bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

Requesting review from QA contact:
/cc @kasturinarra

In response to this:

/bugzilla 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.

[damemi]

/hold
Something weird about how I tried to break out the common config in the first commit broke this in all the clusters I tried, but copying it to each profile seems to have fixed it. Want to examine more before merging but it seems like the 2nd commit works at least

[damemi]

/hold cancel
tests are green now, this is ready to tag

[damemi]

/retest

[ravisantoshgudimetla]

/lgtm

Thank you for working on this @damemi

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: damemi, ravisantoshgudimetla

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 [damemi]

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

[openshift-ci]

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

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

Bugzilla bug 1984608 has been moved to the MODIFIED state.

In response to this:

Bug 1984608: Set kube-scheduler leader election defaults

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.