pkg log/syslog (darwin-arm64), method (*Writer) Emerg(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Err(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Info(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Notice(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Warning(string) error
pkg log/syslog (darwin-arm64), method (*Writer) Write([]uint8) (int, error)

  
  <mime-type type="application/vnd.sun.xml.writer">
    <sub-class-of type="application/zip"/>
    <glob pattern="*.sxw"/>
  </mime-type>
  <!-- can't currently find any diff in contents btwn writer
    and template. Must rely on extension -->
  <mime-type type="application/vnd.sun.xml.writer.template">
    <sub-class-of type="application/vnd.sun.xml.writer"/>
    <glob pattern="*.stw"/>
  </mime-type>

### SIG Cluster Lifecycle

For 1.13 SIG Cluster Lifecycle is pleased to announce the long awaited promotion of kubeadm to stable GA, and the promotion of kubeadm’s configuration API to `v1beta1`.

- Server Side Apply now treats all <Some>Selector fields as atomic (meaning the entire selector is managed by a single writer and updated together), since they contain interrelated and inseparable fields that do not merge in intuitive ways. ([#97989](https://github.com/kubernetes/kubernetes/pull/97989), [@Danil-Grigorev](https://github.com/Danil-Grigorev)) [SIG API Machinery]...

* The metrics APIs, `custom-metrics.metrics.k8s.io` and `metrics`, were moved from `v1alpha1` to `v1beta1`, and renamed to `custom.metrics.k8s.io` and `metrics.k8s.io`, respectively. If you have deployed a custom metrics adapter, ensure that it supports the new API version. If you have deployed Heapster in aggregated API server mode, upgrade Heapster to support the latest API version.

* Fix adding disks to more than one scsi adapter. ([#42422](https://github.com/kubernetes/kubernetes/pull/42422), [@kerneltime](https://github.com/kerneltime))

etes/issues/61446)) and with containerized kubelets ([#61456](https://github.com/kubernetes/kubernetes/issues/61456)). The workaround for this issue is to specify the complete path in the hostPath volume. Use of subPathmounts nested within atomic writer volumes (configmap, secret, downwardAPI, projected) does not work ([#61545](https://github.com/kubernetes/kubernetes/issues/61545)), and socket files cannot be loaded from a subPath ([#62377](https://github.com/kubernetes/kubernetes/issues/61377))....