### API Change

- '`kube-apiserver`: adds `--authentication-config` flag for reading `AuthenticationConfiguration`
  files. `--authentication-config` flag is mutually exclusive with the existing `--oidc-*`

- Fix: Route controller should update routes with NodeIP changed ([#116361](https://github.com/kubernetes/kubernetes/pull/116361), [@lzhecheng](https://github.com/lzhecheng)) [SIG Cloud Provider]
- Fixes a regression in the pod binding subresource to honor the `metadata.uid` precondition.

- Since golang 1.17 both net.ParseIP and net.ParseCIDR rejects leading zeros in the dot-decimal notation of IPv4 addresses,
  Kubernetes will keep allowing leading zeros on IPv4 address to not break the compatibility.
  IMPORTANT: Kubernetes interprets leading zeros on IPv4 addresses as decimal, users must not rely on parser alignment to not being impacted by the associated security advisory:

*.hosting.myjino.ru
*.hosting.ovh.net
*.id.pub
*.il-central-1.airflow.amazonaws.com
*.in.futurecms.at
*.jm
*.kawasaki.jp
*.kh
*.kin.one
*.kin.pub
*.kitakyushu.jp
*.kobe.jp
*.kunden.ortsinfo.at
*.landing.myjino.ru
*.lcl.dev
*.lclstage.dev
*.linodeobjects.com
*.magentosite.cloud
*.me-central-1.airflow.amazonaws.com
*.me-south-1.airflow.amazonaws.com
*.migration.run
*.mm
*.moonscale.io
*.my.canva.site

the permutation. n, rate int // dsbyte contains the "domain separation" bits and the first bit of // the padding. Sections 6.1 and 6.2 of [1] separate the outputs of the // SHA-3 and SHAKE functions by appending bitstrings to the message. // Using a little-endian bit-ordering convention, these are "01" for SHA-3 // and "1111" for SHAKE, or 00000010b and 00001111b, respectively. Then the // padding rule from section 5.1 is applied to pad the message to a multiple // of the rate, which involves adding...

the permutation. n, rate int // dsbyte contains the "domain separation" bits and the first bit of // the padding. Sections 6.1 and 6.2 of [1] separate the outputs of the // SHA-3 and SHAKE functions by appending bitstrings to the message. // Using a little-endian bit-ordering convention, these are "01" for SHA-3 // and "1111" for SHAKE, or 00000010b and 00001111b, respectively. Then the // padding rule from section 5.1 is applied to pad the message to a multiple // of the rate, which involves adding...

16FE5..16FEF  ; disallowed                             # NA   <reserved-16FE5>..<reserved-16FEF>
16FF0..16FF1  ; valid                                  # 13.0 VIETNAMESE ALTERNATE READING MARK CA..VIETNAMESE ALTERNATE READING MARK NHAY
16FF2..16FFF  ; disallowed                             # NA   <reserved-16FF2>..<reserved-16FFF>