Change:
- `--port` - `--address` The insecure port flags `--port` may only be set to 0 now. <ins> - Kube-scheduler: the `--port` and `--address` flags have no effect and would be removed in v1.24. The insecure port flags `--port` may only be set to 0 now. </ins> Also `metricsBindAddress` and `healthzBindAddress` fields from `kubescheduler.config.k8s.io/v1beta1` are no-op and expected to be empty. Removed in `kubescheduler.config.k8s.io/v1beta2` completely. ([#96345](https://github.com/kubernetes/kubernetes/pull/96345), [@ingvagabund](https://github.com/ingvagabund)) <ins> In addition, please be careful that: - kube-scheduler MUST start with `--authorization-kubeconfig` and `--authentication-kubeconfig` correctly set to get authentication/authorization working. - liveness/readiness probes to kube-scheduler MUST use HTTPS now, and the default port has been changed to 10259. - Applications that fetch metrics from kube-scheduler should use a dedicated service account which is allowed to access nonResourceURLs `/metrics`. ([#96345](https://github.com/kubernetes/kubernetes/pull/96345), [@ingvagabund](https://github.com/ingvagabund)) [SIG Cloud Provider, Scheduling and Testing] </ins> - Feature-gate `VolumeSubpath` has been deprecated and cannot be disabled. It will be completely removed in 1.25 ([#105474](https://github.com/kubernetes/kubernetes/pull/105474), [@mauriciopoppe](https://github.com/mauriciopoppe)) - Kubeadm: add a new `output/v1alpha2` API that is identical to the `output/v1alpha1`, but attempts to resolve some internal dependencies with the `kubeadm/v1beta2` API. The `output/v1alpha1` API is now deprecated and will be removed in a future release. ([#105295](https://github.com/kubernetes/kubernetes/pull/105295), [@neolit123](https://github.com/neolit123)) - Kubeadm: add the kubeadm specific, Alpha (disabled by default) feature gate UnversionedKubeletConfigMap. When this feature is enabled kubeadm will start using a new naming format for the ConfigMap where it stores the KubeletConfiguration structure. The old format included the Kubernetes version - "kube-system/kubelet-config-1.22", while the new format does not - "kube-system/kubelet-config". A similar formatting change is done for the related RBAC rules. The old format is now DEPRECATED and will be removed after the feature graduates to GA. When writing the ConfigMap kubeadm (init, upgrade apply) will respect the value of UnversionedKubeletConfigMap, while when reading it (join, reset, upgrade), it would attempt to use new format first and fallback to the legacy format if needed. ([#105741](https://github.com/kubernetes/kubernetes/pull/105741), [@neolit123](https://github.com/neolit123)) [SIG Cluster Lifecycle and Testing]

Discussion:
It looks like default HTTPS port for kube-scheduler has changed from to between 1.22.4 and 1.23.0 releases and it has not been mentioned in the changelog. EDIT: Actually, I see now that 1.22.4 listens on , but also on and 1.23.0 just stopped listening on . Breaking changes to be included in the changelog. With kube-prometheus-stack installed, with kube-scheduler scraping configured, upgrade kube-scheduler from 1.22.4 to 1.23.0. No response <details</details<details</details<details</details<details</details<details</details<details</details
This issue is currently awaiting triage. If a SIG or subproject determines this is a relevant issue, they will accept it by applying the label and provide further guidance. The label can be by org members by writing in a comment. <detailsInstructions for interacting with me using PR comments are available . If you have questions or suggestions related to my behavior, please file an issue against the repository. </details
/sig release scheduling
was the change, and included a detailed release note. Did that not get pulled into the release notes automatically? /sig docs release
can you help update the 1.23 release notes with the content from in the "Action required" section?
/assign ingvagabund
I see now that it has indeed been mentioned for , here: but not for .
weird, v1.23.0 is supposed to roll up all the intermediate notes.
Is it sufficient to manually edit and extend
manual edit is fine, hoist it to the section