- When using `kubectl replace` (or the equivalent API call) on a Service, the caller no longer needs to do a read-modify-write cycle to fetch the allocated values for `.spec.clusterIP` and `.spec.ports[].nodePort`.  Instead the API server will automatically carry these forward from the original object when the new object does not specify them. ([#104672](https://github.com/kubernetes/kubernetes/pull/104672),...

{
  "components": {
    "schemas": {
      "io.k8s.api.core.v1.TypedLocalObjectReference": {
        "description": "TypedLocalObjectReference contains enough information to let you locate the typed referenced object inside the same namespace.",
        "properties": {
          "apiGroup": {

{
  "components": {
    "schemas": {
      "io.k8s.api.rbac.v1.AggregationRule": {
        "description": "AggregationRule describes how to locate ClusterRoles to aggregate into the ClusterRole",
        "properties": {
          "clusterRoleSelectors": {
            "description": "ClusterRoleSelectors holds a list of selectors which will be used to find ClusterRoles and create the rules. If any of the selectors match, then the ClusterRole's permissions will be added",

          }
        },
        "type": "object",
        "x-kubernetes-map-type": "atomic"
      },
      "io.k8s.api.admissionregistration.v1.ParamRef": {
        "description": "ParamRef describes how to locate the params to be used as input to expressions of rules applied by a policy binding.",
        "properties": {
          "name": {

    * This was reported internally by [@rushilsrivastava](https://github.com/rushilsrivastava) as a memory leak when the server had unhandled exceptions that would produce internal server errors, the memory allocated before that point would not be released.
    * Read the new docs: [Dependencies with `yield` and `except`](https://fastapi.tiangolo.com/tutorial/dependencies/dependencies-with-yield/#dependencies-with-yield-and-except).