Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

sched: --leader-elect flag is not honored well #105704

Closed
Huang-Wei opened this issue Oct 15, 2021 · 4 comments · Fixed by #105712 or #105915
Closed

sched: --leader-elect flag is not honored well #105704

Huang-Wei opened this issue Oct 15, 2021 · 4 comments · Fixed by #105712 or #105915
Assignees
@Huang-Wei
Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.

Comments

@Huang-Wei
Copy link
Member

What happened?

When --leader-elect=false is specified to start the scheduler, it's not honored well - the scheduler still tries to acquire leader election obj and it causes the scheduler to fail scheduling pods.

What did you expect to happen?

The --leader-elect flag is always honored, no matter its corresponding fields in ComponentConfig is set or not.

How can we reproduce it (as minimally and precisely as possible)?

See detailed steps reported by the user: kubernetes/website#29342 (comment)

Anything else we need to know?

No response

Kubernetes version

This issue occurs in k8s version >= 1.22.

Cloud provider

OS version

# On Linux:
$ cat /etc/os-release
# paste output here
$ uname -a
# paste output here

# On Windows:
C:\> wmic os get Caption, Version, BuildNumber, OSArchitecture
# paste output here

Install tools

Container runtime (CRI) and and version (if applicable)

Related plugins (CNI, CSI, ...) and versions (if applicable)
@Huang-Wei Huang-Wei added the kind/bug Categorizes issue or PR as related to a bug. label Oct 15, 2021
@k8s-ci-robot k8s-ci-robot added the needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. label Oct 15, 2021
@k8s-ci-robot
Copy link
Contributor

@Huang-Wei: This issue is currently awaiting triage.

If a SIG or subproject determines this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

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.

@k8s-ci-robot k8s-ci-robot added the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Oct 15, 2021
@Huang-Wei
Copy link
Member Author

/sig scheduling
/assign
cc/ @alculquicondor @chirangaalwis

@k8s-ci-robot k8s-ci-robot added sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling. and removed needs-sig Indicates an issue or PR lacks a `sig/foo` label and requires one. labels Oct 15, 2021
@Huang-Wei Huang-Wei mentioned this issue Oct 16, 2021
Merged
@Huang-Wei Huang-Wei mentioned this issue Oct 26, 2021
Merged
@Huang-Wei
Copy link
Member Author

/reopen

@k8s-ci-robot k8s-ci-robot reopened this Oct 29, 2021
@k8s-ci-robot
Copy link
Contributor

@Huang-Wei: Reopened this issue.

In response to this:

/reopen

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@Huang-Wei Huang-Wei

Labels
kind/bug Categorizes issue or PR as related to a bug. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. sig/scheduling Categorizes an issue or PR as relevant to SIG Scheduling.
Projects
None yet
Milestone
No milestone
2 participants
@Huang-Wei @k8s-ci-robot