Thanks to visit codestin.com
Credit goes to github.com

Skip to content

kube-scheduler default port (breaking) change not mentioned in 1.23 changelog #106885

@invidian

Description

@invidian

What happened?

It looks like default HTTPS port for kube-scheduler has changed from 10251 to 10259 between 1.22.4 and 1.23.0 releases and it has not been mentioned in the changelog.

I1208 11:30:46.202095       1 deprecated_insecure_serving.go:54] Serving healthz insecurely on [::]:10251
I1208 09:17:41.523334       1 secure_serving.go:200] Serving securely on [::]:10259

EDIT: Actually, I see now that 1.22.4 listens on 10259, but also on 10251 and 1.23.0 just stopped listening on 10251.

What did you expect to happen?

Breaking changes to be included in the changelog.

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

With kube-prometheus-stack installed, with kube-scheduler scraping configured, upgrade kube-scheduler from 1.22.4 to 1.23.0.

Anything else we need to know?

No response

Kubernetes version

$ kubectl version
Client Version: version.Info{Major:"1", Minor:"22", GitVersion:"v1.22.4", GitCommit:"b695d79d4f967c403a96986f1750a35eb75e75f1", GitTreeState:"archive", BuildDate:"2021-11-18T21:20:32Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"}
Server Version: version.Info{Major:"1", Minor:"23", GitVersion:"v1.23.0", GitCommit:"ab69524f795c42094a6630298ff53f3c3ebab7f4", GitTreeState:"clean", BuildDate:"2021-12-07T18:09:57Z", GoVersion:"go1.17.3", Compiler:"gc", Platform:"linux/amd64"}

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)

Metadata

Metadata

Assignees

Labels

kind/documentationCategorizes issue or PR as related to documentation.needs-triageIndicates an issue or PR lacks a `triage/foo` label and requires one.priority/important-soonMust be staffed and worked on either currently, or very soon, ideally in time for the next release.sig/docsCategorizes an issue or PR as relevant to SIG Docs.sig/releaseCategorizes an issue or PR as relevant to SIG Release.sig/schedulingCategorizes an issue or PR as relevant to SIG Scheduling.

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions