Comment 5 for bug 2056326

Reviewed: https://review.opendev.org/c/starlingx/stx-puppet/+/911945
Committed: https://opendev.org/starlingx/stx-puppet/commit/6c15b7a41b950a102e96e55d16be4df8acffe06b
Submitter: "Zuul (22348)"
Branch: master

commit 6c15b7a41b950a102e96e55d16be4df8acffe06b
Author: Saba Touheed Mujawar <email address hidden>
Date: Thu Mar 7 11:39:15 2024 -0500

    Set Kubernetes control-plane upgrade timeout to 210s

    In the case of a rare intermittent failure behaviour during the
    upgrading control plane step where puppet hits timeout first before
    the upgrade is completed or kubeadm hits its own Upgrade Manifest
    timeout (at 5m).

    This change sets puppet timeouts slightly larger than the
    engineered kubeadm timeout settings. Typical puppet apply times
    are less than 90 seconds, though we have seen infrequent outliers
    hit the default 5m timeout.

    We engineer the timeout for kubeadm-upgrade-apply and
    kubeadm-upgrade-node to 210 seconds, based on setting 3 minute
    kubeadm UpgrademManifestTimeout and 30 second buffer.

    Note: 'kubeadm-upgrade-apply' and 'kubeadm-upgrade-node' take the
          same amount of time for the control-plane upgrade.

    TEST PLAN:
    PASS: Perform k8s upgrade and verify puppet does not timeout
          before kubeadm-upgrade-apply and kubeadm-upgrade-node .

    Partial-Bug: 2056326

    Change-Id: Iec60476c964140f7b717c6d4dcdb266b0229b556
    Signed-off-by: Saba Touheed Mujawar <email address hidden>