Skip to content

Commit cd65410

Browse files
committed
edit release demotion description
1 parent 1e49b9a commit cd65410

File tree

1 file changed

+7
-1
lines changed

1 file changed

+7
-1
lines changed

docs/vendor/releases-about.mdx

Lines changed: 7 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -86,7 +86,13 @@ The following describes how each installation method handles a demoted release:
8686

8787
* **Helm CLI**: When a release is demoted, it is no longer listed in the customer's Enterprise Portal as available for update, unless the customer had already downloaded the release before it was demoted.
8888

89-
* **Embedded Cluster, Existing Cluster KOTS, and kURL**: When a release is demoted, it is removed from the list of available updates in the Admin Console the next time that an upstream version check occurs, unless the customer had already deployed the release before it was demoted.
89+
* **Embedded Cluster**: When a release is demoted, it is removed from the list of available updates in the Admin Console the next time that an upstream version check occurs, unless the customer had already deployed the release before it was demoted.
90+
91+
* **Existing Cluster KOTS and kURL (KOTS 1.128.0 and Later)**: In KOTS existing cluster and kURL installations that use KOTS 1.128.0 or later, when a release is demoted, it is removed from the list of available updates in the Admin Console the next time that an upstream version check occurs, unless the customer had already deployed the release before it was demoted.
92+
93+
* **Existing Cluster KOTS and kURL (KOTS 1.127.2 and Earlier)**: In KOTS existing cluster and kURL installations that use KOTS 1.127.2 or earlier, after the Admin Console checks for upstream updates, it automatically downloads metadata for the newly-available releases. Therefore, whether or not the customer can see a demoted release in the Admin Console depends on the last time the customer checked for updates:
94+
* If the customer checked for updates and fetched a release _before_ it was demoted, then the release will remain listed in the Admin Console the next time an update check occurs. This is because a release cannot be withdrawn from the customer’s environment after it has been downloaded.
95+
* If the customer checks for udpates _after_ a release was demoted, then the demoted release is not fetched and is not listed in the Admin Console.
9096

9197
### Archived Releases
9298

0 commit comments

Comments
 (0)