- increases the weight of user specifiable priorities.
  The weights of following priority plugins are increased
    - `TaintTolerations` to 3 - as leveraging node tainting to group nodes in the cluster is becoming a widely-adopted practice
    - `NodeAffinity` to 2
    - `InterPodAffinity` to 2
  

        *   `CategoryEncoding` no longer supports `adapt`, `IntegerLookup` now
            supports equivalent functionality. `max_tokens` argument renamed to
            `num_tokens`.
        *   `Discretization` added `num_bins` argument for learning bins
            boundaries through calling `adapt` on a dataset. Renamed `bins`
            argument to `bin_boundaries` for specifying bins without `adapt`.
    *   Improvements to model saving/loading:

### Instrumentation

In v1.9 we focused on improving stability of the components owned by the SIG, including Heapster, Custom Metrics API adapters for Prometheus, and Stackdriver.

### Network

- The kube-controller-manager's deprecated `--experimental-cluster-signing-duration` flag is now removed. Adapt your machinery to use the `--cluster-signing-duration` flag that is available since v1.19. ([#108476](https://github.com/kubernetes/kubernetes/pull/108476), [@ialidzhikov](https://github.com/ialidzhikov))

gb.net
hu.net
jp.net
jpn.com
mex.com
ru.com
sa.com
se.net
uk.com
uk.net
us.com
za.bz
za.com

// No longer operated by CentralNic, these entries should be adopted and/or removed by current operators
// Submitted by Gavin Brown <******@****.***>
ar.com
hu.com
kr.com
no.com
qc.com
uy.com

      <match value="\\section" type="string" offset="0"/>
      <match value="\\setlength" type="string" offset="0"/>
      <match value="\\documentstyle" type="string" offset="0"/>
      <match value="\\chapter" type="string" offset="0"/>
      <match value="\\documentclass" type="string" offset="0"/>
      <match value="\\relax" type="string" offset="0"/>
      <match value="\\contentsline" type="string" offset="0"/>

### Structured Logging in Kubelet

  
  Users who maintain controllers which relied on the fact that pods with RestartPolicy=Always
  never enter the Succeeded phase may need to adapt their controllers. This is because as a consequence of 
  the change pods which use RestartPolicy=Always may end up in the Succeeded phase in two scenarios: pod 

### Kubernetes release cadence change

javax.annotation.processing,\ javax.jws,\ javax.jws.soap,\ javax.lang.model,\ javax.lang.model.element,\ javax.lang.model.type,\ javax.lang.model.util,\ javax.script,\ javax.tools,\ javax.xml.bind,\ javax.xml.bind.annotation,\ javax.xml.bind.annotation.adapters,\ javax.xml.bind.attachment,\ javax.xml.bind.helpers,\ javax.xml.bind.util,\ javax.xml.crypto,\ javax.xml.crypto.dom,\ javax.xml.crypto.dsig,\ javax.xml.crypto.dsig.dom,\ javax.xml.crypto.dsig.keyinfo,\ javax.xml.crypto.dsig.spec,\ javax.xml.soap,\...