registration.updateHeartbeat();

        // After update, should not be expired with long timeout
        assertFalse(registration.isExpired(60000));

        // Verify heartbeat was actually updated
        assertTrue(registration.getLastHeartbeat() > initialTime);
    }

    @Test
    void testExpiration() throws InterruptedException {

    /** WitnessUnregister operation number */
    public static final int WITNESS_UNREGISTER = 1;
    /** WitnessAsyncNotify operation number */
    public static final int WITNESS_ASYNC_NOTIFY = 2;
    /** Witness heartbeat operation number */
    public static final int WITNESS_HEARTBEAT = 3;

    // Common return codes from MS-SWN specification
    /** Operation completed successfully */
    public static final int ERROR_SUCCESS = 0x00000000;

    /**
     * @return timeout for persistent handles in milliseconds
     */
    long getPersistentHandleTimeout();

    /**
     * Gets the witness heartbeat timeout in milliseconds.
     *
     * @return the heartbeat timeout
     */
    long getWitnessHeartbeatTimeout();

    /**
     * Gets the witness registration timeout in milliseconds.
     *
     * @return the registration timeout

    /**
     * Flag indicating whether SMB Witness protocol should be used for failover
     */
    protected boolean useWitness = false; // Disabled by default
    /**
     * Timeout in milliseconds for witness heartbeat messages
     */
    protected long witnessHeartbeatTimeout = 120000; // 2 minutes
    /**
     * Timeout in milliseconds for witness registration
     */

focused on stability and performance improvements in the 1.13 release.  A new alpha feature is introduced to improve the mechanism that nodes heartbeat back to the control plane.  The `NodeLease` feature results in the node using a `Lease` resource in the `kube-node-lease` namespace that is renewed periodically.  The `NodeStatus` that was used previously to heartbeat back to the control plane is only updated when it changes.  This reduces load on the control plane for large clusters. The Kubelet plugin...

search_engine.http.ssl.certificate_authorities=
# Username for authenticating to the search engine.
search_engine.username=
# Password for authenticating to the search engine.
search_engine.password=
# Interval (ms) for heartbeat checks to the search engine.
search_engine.heartbeat_interval=10000

# Cipher algorithm used for encryption.
app.cipher.algorism=aes
# Secret key for encryption (change this value for production).

- kubelet: fix fail to close kubelet->API connections on heartbeat failure when bootstrapping or client certificate rotation is disabled ([#78016](https://github.com/kubernetes/kubernetes/pull/78016), [@gaorong](https://github.com/gaorong))

    Integer getSearchEnginePasswordAsInteger();

    /**
     * Get the value for the key 'search_engine.heartbeat_interval'. <br>
     * The value is, e.g. 10000 <br>
     * comment: Interval (ms) for heartbeat checks to the search engine.
     * @return The value of found property. (NotNull: if not found, exception but basically no way)
     */
    String getSearchEngineHeartbeatInterval();

    /**

* fix azure retry issue when return 2XX with error ([#78298](https://github.com/kubernetes/kubernetes/pull/78298), [@andyzhangx](https://github.com/andyzhangx))
* kubelet: fix fail to close kubelet->API connections on heartbeat failure when bootstrapping or client certificate rotation is disabled ([#78016](https://github.com/kubernetes/kubernetes/pull/78016), [@gaorong](https://github.com/gaorong))

- The kubelet no longer forcefully closes active connections on heartbeat failures, using the HTTP2 health check mechanism to detect broken connections. Users can force the previous behavior of the kubelet by setting the environment variable DISABLE_HTTP2. ([#108107](https://github.com/kubernetes/kubernetes/pull/108107),...