total number of nodes that should be running the daemon pod (i.e. status.desiredNumberScheduled) can have their a new pod created before the old pod is marked as deleted. The update starts by launching new pods on 30% of nodes. Once an updated pod is available (Ready for at least minReadySeconds) the old DaemonSet pod on that node is marked deleted. If the old pod becomes unavailable for any reason (Ready transitions to false, is evicted, or is drained) an updated pod is immediatedly created on that...

*   `tf.keras.optimizers.Optimizer` now points to the new Keras optimizer, and
    old optimizers have moved to the `tf.keras.optimizers.legacy` namespace.
    If you find your workflow failing due to this change,
    you may be facing one of the following issues:

    *   **Checkpoint loading failure.** The new optimizer handles optimizer
        state differently from the old optimizer, which simplies the logic of