pkg syscall (netbsd-arm64-cgo), const DLT_LINUX_SLL = 113
pkg syscall (netbsd-arm64-cgo), const DLT_LINUX_SLL ideal-int
pkg syscall (netbsd-arm64-cgo), const DLT_LOOP = 108
pkg syscall (netbsd-arm64-cgo), const DLT_LOOP ideal-int
pkg syscall (netbsd-arm64-cgo), const DLT_LTALK = 114
pkg syscall (netbsd-arm64-cgo), const DLT_LTALK ideal-int
pkg syscall (netbsd-arm64-cgo), const DLT_MFR = 182

pkg syscall (darwin-arm64), const DLT_LINUX_SLL = 113
pkg syscall (darwin-arm64), const DLT_LINUX_SLL ideal-int
pkg syscall (darwin-arm64), const DLT_LOOP = 108
pkg syscall (darwin-arm64), const DLT_LOOP ideal-int
pkg syscall (darwin-arm64), const DLT_NULL = 0
pkg syscall (darwin-arm64), const DLT_NULL ideal-int
pkg syscall (darwin-arm64), const DLT_PFLOG = 117

* Fixes [#49418](https://github.com/kubernetes/kubernetes/pull/49418) where kube-controller-manager can panic on volume.CanSupport methods and enter a crash loop. ([#49420](https://github.com/kubernetes/kubernetes/pull/49420), [@gnufied](https://github.com/gnufied))

## Changelog since v1.8.9

### Other notable changes

* gce: fixes race condition in ServiceController, where nodes weren't updated in the node sync loop, by updating TargetPools in the ensureExternalLoadBalancer call. ([#58368](https://github.com/kubernetes/kubernetes/pull/58368), [@MrHohn](https://github.com/MrHohn))

</pre>

<h3 id="Continue_statements">Continue statements</h3>

<p>
A "continue" statement begins the next iteration of the
innermost enclosing <a href="#For_statements">"for" loop</a>
by advancing control to the end of the loop block.
The "for" loop must be within the same function.
</p>

<pre class="ebnf">
ContinueStmt = "continue" [ Label ] .
</pre>

<p>

    * The vSphere cloud provider has a cleanup function with a loop,
    * inside of which a write lock was intended to prevent races against
    * VM creation, but the usage of the sync.RWMutex type is incorrect,
    * plus is placed in a defer call so the locking is effectively
    * nonexistent.  This patch adds an anonymous function call inside
    * the loop to correctly handle acquiring the write lock with deferred

    * The vSphere cloud provider has a cleanup function with a loop,
    * inside of which a write lock was intended to prevent races against
    * VM creation, but the usage of the sync.RWMutex type is incorrect,
    * plus is placed in a defer call so the locking is effectively
    * nonexistent.  This patch adds an anonymous function call inside
    * the loop to correctly handle acquiring the write lock with deferred

* change default azure file mount permission to 0777 ([#69854](https://github.com/kubernetes/kubernetes/pull/69854), [@andyzhangx](https://github.com/andyzhangx))
* Fix a bug in the scheduler that could cause the scheduler to go to an infinite loop when all nodes in a zone are removed. ([#69758](https://github.com/kubernetes/kubernetes/pull/69758), [@bsalamat](https://github.com/bsalamat))

- Fixed 'kubeadm upgrade' infinite loop waiting for pod restart ([#69886](https://github.com/kubernetes/kubernetes/pull/69886), [@bart0sh](https://github.com/bart0sh))

- Fixed bug in CPUManager with race on container map access ([#97427](https://github.com/kubernetes/kubernetes/pull/97427), [@klueska](https://github.com/klueska)) [SIG Node]