* kube-apiserver: a request body of a CREATE/UPDATE/PATCH/DELETE resource operation larger than 100 MB will return a 413 "request entity too large" error. ([#73805](https://github.com/kubernetes/kubernetes/pull/73805), [@caesarxuchao](https://github.com/caesarxuchao))

- When the kubelet fails to assign CPUs to a Pod because there less available CPUs than the Pod requests, the error message changed from
  `not enough cpus available to satisfy request` to `not enough cpus available to satisfy request: <num_requested> requested, only <num_available> available`. ([#121059](https://github.com/kubernetes/kubernetes/pull/121059), [@matte21](https://github.com/matte21))

suggest.field.roles=role
# Index contents for suggestion.
suggest.field.index.contents=content,title
# Interval for suggestion update requests.
suggest.update.request.interval=0
# Number of documents per suggestion update request.
suggest.update.doc.per.request=2
# Percentage limit for suggestion update contents.
suggest.update.contents.limit.num.percentage=50%
# Maximum number of suggestion update contents.

### Feature

- Kube-apiserver: Added Alpha features to allow API server authz to check the context of requests:
  - The `AuthorizeWithSelectors` feature gate enables including field and label selector information from requests in webhook authorization calls.

        }
    }

    /**
     * Executes a request within the context of an open file handle
     *
     * @param <T> the response type
     * @param th the tree handle
     * @param first the first request to execute
     * @param others additional requests to chain
     * @return the response from the first request
     * @throws CIFSException if an error occurs
     */

- Apiserver add a new flag --goaway-chance which is the fraction of requests that will be closed gracefully(GOAWAY) to prevent HTTP/2 clients from getting stuck on a single apiserver. 
  After the connection closed(received GOAWAY), the client's other in-flight requests won't be affected, and the client will reconnect. 
  The flag min value is 0 (off), max is .02 (1/50 requests); .001 (1/1000) is a recommended starting point.

- Kubeadm: make sure that a variety of API server requests are retried during "init", "join", "upgrade", "reset" workflows. Prior to this change some API server requests, such as, creating or updating ConfigMaps were "one-shot"...

  - Adds apiserver.latency.k8s.io/authorization annotation to the audit log to record the time spent authorizing slow requests. ([#130571](https://github.com/kubernetes/kubernetes/pull/130571), [@hakuna-matatah](https://github.com/hakuna-matatah)) [SIG Auth]

     * Get the value for the key 'rate.limit.requests.per.window'. <br>
     * The value is, e.g. 100 <br>
     * comment: Maximum number of requests allowed per window.
     * @return The value of found property. (NotNull: if not found, exception but basically no way)
     */
    String getRateLimitRequestsPerWindow();

    /**
     * Get the value for the key 'rate.limit.requests.per.window' as {@link Integer}. <br>