*   Azure Load Balancer Auto Mode: Services can be annotated to allow auto selection of available load balancers and to provide specific availability sets that host the load balancers (for example, `service.beta.kubernetes.io/azure-load-balancer-mode=auto|as1,as2...`)

### **CLI**

#### **Kubectl**

    /** The key of the configuration. e.g. 5 */
    String INDEX_number_of_shards = "index.number_of_shards";

    /** The key of the configuration. e.g. 0-1 */
    String INDEX_auto_expand_replicas = "index.auto_expand_replicas";

    /** The key of the configuration. e.g. SHA-512 */
    String INDEX_ID_DIGEST_ALGORITHM = "index.id.digest.algorithm";

    /** The key of the configuration. e.g. admin */

     disabled by setting the `--horizontal-pod-autoscaler-use-rest-clients` flag to `false`.

### Cluster Lifecycle

- The `auto-detect` behavior of the kubelet's `--cloud-provider` flag is deprecated.

  - In version 1.8, the default value for the kubelet's `--cloud-provider` flag is `auto-detect`. Be aware that it works only on GCE, AWS and Azure.

- Upgrades `IPv6Dualstack` to `Beta` and turns it on by default. New clusters or existing clusters are not be affected until an actor starts adding secondary Pods and service CIDRS CLI flags as described here: [IPv4/IPv6 Dual-stack](https://github.com/kubernetes/enhancements/tree/master/keps/sig-network/563-dual-stack) ([#98969](https://github.com/kubernetes/kubernetes/pull/98969),...

- `kube-controller-manager`: The `LegacyServiceAccountTokenCleanUp` feature gate is now `beta` and enabled by default. When enabled, legacy auto-generated service account token secrets are auto-labeled with a `kubernetes.io/legacy-token-invalid-since` label if the credentials have not been used in the time specified by `--legacy-service-account-token-clean-up-period` (defaulting to one year), **and** are referenced...

* Make logdump support kubemark and support gke with 'use_custom_instance_list' ([#51834](https://github.com/kubernetes/kubernetes/pull/51834), [@shyamjvs](https://github.com/shyamjvs))
* Fixes an issue with APIService auto-registration affecting rolling HA apiserver restarts that add or remove API groups being served. ([#51921](https://github.com/kubernetes/kubernetes/pull/51921), [@liggitt](https://github.com/liggitt))

    dep ->> operation: Run dependency, e.g. DB session
    opt raise
        operation -->> dep: Raise HTTPException
        dep -->> handler: Auto forward exception
        handler -->> client: HTTP error response
        operation -->> dep: Raise other exception
        dep -->> handler: Auto forward exception
    end
    operation ->> client: Return response to client

pkg syscall (netbsd-arm64-cgo), const RLIMIT_STACK = 3
pkg syscall (netbsd-arm64-cgo), const RLIMIT_STACK ideal-int
pkg syscall (netbsd-arm64-cgo), const RTA_AUTHOR = 64
pkg syscall (netbsd-arm64-cgo), const RTA_AUTHOR ideal-int
pkg syscall (netbsd-arm64-cgo), const RTA_BRD = 128
pkg syscall (netbsd-arm64-cgo), const RTA_BRD ideal-int
pkg syscall (netbsd-arm64-cgo), const RTA_DST = 1

pkg syscall (darwin-arm64), const RLIM_INFINITY = 9223372036854775807
pkg syscall (darwin-arm64), const RLIM_INFINITY ideal-int
pkg syscall (darwin-arm64), const RTAX_AUTHOR = 6
pkg syscall (darwin-arm64), const RTAX_AUTHOR ideal-int
pkg syscall (darwin-arm64), const RTAX_BRD = 7
pkg syscall (darwin-arm64), const RTAX_BRD ideal-int
pkg syscall (darwin-arm64), const RTAX_DST = 0

  // +optional
  optional k8s.io.apimachinery.pkg.apis.meta.v1.ObjectMeta metadata = 1;

  // spec defines the desired characteristics of a volume requested by a pod author.
  // More info: https://kubernetes.io/docs/concepts/storage/persistent-volumes#persistentvolumeclaims
  // +optional
  optional PersistentVolumeClaimSpec spec = 2;