A MicroShift cluster with customized featuregates will refuse to boot after upgrading major/minor version. This (mostly) aligns with OpenShift but the policy does not leave room for customers granted support exceptions for specific features.

Customers must be able to upgrade their clusters when those clusters have customized feature gates covered by that customer's support exception.

    100%

Assumption: MicroShift rpm installation (ostree installs are also affected).

    1. Deploy and start MicroShift
    2. Set a custom feature gate:

$ cat > /etc/microshift/config.d/featuregate.yaml <<'EOF'
apiServer:
  featureGates:
    featureSet: CustomNoUpgrade
    customNoUpgrade:
      enabled: [ "ShinyFeature" ]

    3. Restart Microshift

$ sudo systemctl restart microshift

    4. Upgrade MicroShift

$ sudo dnf upgrade microshift

    5. Check microshift.service status and logs

$ sudo systemctl status microshift
$ sudo journalctl -fu microshift

     MicroShift will fail to start and logging will indicate that an upgrade was detected after custom featuregates were set.

    For customers with support exceptions, an upgraded microshift cluster should start.