pkg log/syslog (netbsd-arm64-cgo), method (*Writer) Emerg(string) error
pkg log/syslog (netbsd-arm64-cgo), method (*Writer) Err(string) error
pkg log/syslog (netbsd-arm64-cgo), method (*Writer) Info(string) error
pkg log/syslog (netbsd-arm64-cgo), method (*Writer) Notice(string) error
pkg log/syslog (netbsd-arm64-cgo), method (*Writer) Warning(string) error

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)

	Read(p []byte) (n int, err error)
	Close() error
}

type Writer interface {
	Write(p []byte) (n int, err error)
	Close() error
}

// ReadWriter's methods are Read, Write, and Close.
type ReadWriter interface {
	Reader  // includes methods of Reader in ReadWriter's method set
	Writer  // includes methods of Writer in ReadWriter's method set
}
</pre>

<p>

- 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]...

- Server Side Apply now treats LabelSelector 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. ([#93901](https://github.com/kubernetes/kubernetes/pull/93901), [@jpbetz](https://github.com/jpbetz)) [SIG API Machinery, Auth, CLI,...

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))....

    * Logs are written 1 at a time (no batching)
    * Only a single writer process (lock contention)
* Forget rate limit when CRD establish controller successfully updated CRD condition ([#67370](https://github.com/kubernetes/kubernetes/pull/67370), [@yue9944882](https://github.com/yue9944882))