- Fix issues when supported huge page sizes changes ([#80831](https://github.com/kubernetes/kubernetes/pull/80831), [@odinuge](https://github.com/odinuge)) [SIG Node and Testing]
- Fix kube-apiserver startup to wait for APIServices to be installed into the HTTP handler before reporting readiness. ([#89147](https://github.com/kubernetes/kubernetes/pull/89147), [@sttts](https://github.com/sttts)) [SIG API Machinery]

		{"(*PathError).Timeout", Method, 10},
		{"(*PathError).Unwrap", Method, 13},
		{"(*Process).Kill", Method, 0},
		{"(*Process).Release", Method, 0},
		{"(*Process).Signal", Method, 0},
		{"(*Process).Wait", Method, 0},
		{"(*ProcessState).ExitCode", Method, 12},
		{"(*ProcessState).Exited", Method, 0},
		{"(*ProcessState).Pid", Method, 0},
		{"(*ProcessState).String", Method, 0},

          {{- else if $holdProxy }}
            lifecycle:
              postStart:
                exec:
                  command:
                  - pilot-agent
                  - wait
          {{- else if $nativeSidecar }}
            {{- /* preStop is called when the pod starts shutdown. Initialize drain. We will get SIGTERM once applications are torn down. */}}
            lifecycle:

	//TODO: FUCOMIP F3, F0                  // dfeb
	//TODO: FUCOMP F2                       // ddea
	//TODO: FUCOMP F3                       // ddeb
	//TODO: FUCOMPP                         // dae9
	//TODO: FWAIT                           // 9b
	FXAM                                    // d9e5
	//TODO: FXCH F2                         // d9ca
	//TODO: FXCH F3                         // d9cb

"podManagementPolicy controls how pods are created during initial scale up, when replacing pods on nodes, or when scaling down. The default policy is `OrderedReady`, where pods are created in increasing order (pod-0, then pod-1, etc) and the controller will wait until each pod is ready before continuing. When scaling down, the pods are removed in the opposite order. The alternative policy is `Parallel` which will create pods in parallel to match the desired scale without waiting, and on scale down will delete...

      (https://www.tensorflow.org/api_docs/python/tf/data/experimental/service)
      to write distributed dataset snapshots. The call is non-blocking and
      returns without waiting for the snapshot to finish. Setting `wait=True` to
      `tf.data.Dataset.load` allows the snapshots to be read while they are
      being written.

### Bug Fixes and Other Changes

* <SIMILAR TO ABOVE SECTION, BUT FOR OTHER IMPORTANT CHANGES / BUG FIXES>

            "description": "If specified, the time in seconds before the operation should be retried. Some errors may indicate the client must take an alternate action - for those errors this field may indicate how long to wait before taking the alternate action.",
            "format": "int32",
            "type": "integer"
          },
          "uid": {