Comment 3 for bug 1986854

Reviewed: https://review.opendev.org/c/starlingx/config/+/853923
Committed: https://opendev.org/starlingx/config/commit/3c8a992c5f8f685b0d5ad9fde8a679979ed7dba3
Submitter: "Zuul (22348)"
Branch: master

commit 3c8a992c5f8f685b0d5ad9fde8a679979ed7dba3
Author: Kaustubh Dhokte <email address hidden>
Date: Mon Aug 22 02:30:15 2022 -0400

    Add upgrade path for feature-gate removal

    The commit https://opendev.org/starlingx/integ/commit/a6a5349d025487672fe818aae36a2020a9f9f08c
    (k8s-1.22.5: remove feature-gates)
    added a script that removes deprecated feature gates which is run during
    upgrade-activate phase of previous upgrade cycle .

    The commit https://opendev.org/starlingx/integ/commit/73632416b3fc5ddaa8e2b4babb93ba00fd6c58ca
    (Preserve kube-apiserver manifest params during upgrade-activate)
    modified the script to preserve the kube-apiserver manifest parameters
    and it is supposed to run in next patch release upgrade.

    This change adds a new 'from_version' for the manifest to run during
    next patch release.

    The previous 'from_version' is still supported as in the future, we will
    need to support CentOS to Debian upgrade.

    Test Plan:
    On CentOS AIO-SX
    PASS: Upgrade Successful. Check if advertise address in
          kube-apiserver manifest before and after running
          upgrade-activate is same.
          Ensure that the seccomp profile configuration is
          removed after upgrade-activate.
          Kube-apiserver is running and cluster is accessible after
          the upgrade.

    Closes-Bug: 1986854

    Signed-off-by: Kaustubh Dhokte <email address hidden>
    Change-Id: I0e40df6e341f2da4f0e7ed4b4803197cd07470d5