This API provided status of etcd, kube-scheduler, and kube-controller-manager components, but only worked when those components were local to the API server, and when kube-scheduler and kube-controller-manager exposed unsecured health endpoints. Instead of this API, etcd health is included in the kube-apiserver health check and kube-scheduler/kube-controller-manager health checks can be made directly against those components' health endpoints. ([#93570](https://github.com/kubernetes/kubernetes/pull/93570),...

*   Introduce the `tf.compat.v1.keras.utils.track_tf1_style_variables`
    decorator, which enables using large classes of tf1-style variable_scope,
    `get_variable`, and `compat.v1.layer`-based components from within TF2
    models running with TF2 behavior enabled.

*   `tf.data`:

    *   tf.data service now supports auto-sharding. Users specify the sharding