* At Metadata audit level or higher, an annotation with key "mutation.webhook.admission.k8s.io/round_{round idx}_index_{order idx}" gets logged with JSON payload indicating a webhook gets invoked for given request and whether it mutated the object or not.

* The Kubelet now exports metrics that report the assigned (`node_config_assigned`), last-known-good (`node_config_last_known_good`), and active (`node_config_active`) config sources, and a metric indicating whether the node is experiencing a config-related error (`node_config_error`). The config source metrics always report the value `1`, and carry the `node_config_name`, `node_config_uid`, `node_config_resource_version`, and `node_config_kubelet_key...

  <mime-type type="application/vnd.oma.poc.final-report+xml"/>
  <mime-type type="application/vnd.oma.poc.groups+xml"/>
  <mime-type type="application/vnd.oma.poc.invocation-descriptor+xml"/>
  <mime-type type="application/vnd.oma.poc.optimized-progress-report+xml"/>
  <mime-type type="application/vnd.oma.xcap-directory+xml"/>
  <mime-type type="application/vnd.omads-email+xml"/>

  headers and changing the scheme to `HTTPS`, consistent with container
  startup/readiness/liveness probe capabilities. Lifecycle handlers configured
  with `scheme: HTTPS` that encounter errors indicating the endpoint is actually
  using HTTP fall back to making the request over HTTP for compatibility with
  previous releases. When this happens, a `LifecycleHTTPFallback` event is recorded