Marking a release as no longer required in KOTS 1.126.0 and later #3507
Conversation
✅ Deploy Preview for replicated-docs ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
✅ Deploy Preview for replicated-docs-upgrade ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
replicated-ci
added
type::docs
| * After users deploy a required version, they can no longer redeploy (roll back to) versions earlier than the required version, even if `allowRollback` is true in the Application custom resource manifest. For more information, see [`allowRollback`](/reference/custom-resource-application#allowrollback) in the Application custom resource topic. | ||
| * If you change the channel an existing customer is assigned to, the Admin Console always fetches the latest release on the new channel, regardless of any required releases on the channel. For more information, see [Channel Assignment](licenses-about#channel-assignment) in _About Customers_. | ||
| * Required releases are supported for KOTS installations only and are not supported for releases installed with Helm. The **Prevent this release from being skipped during upgrades** option has no affect if the user installs with Helm. | ||
| * Required releases are not supported for Helm CLI installations. The **Prevent this release from being skipped during upgrades** option has no affect when the user installs with Helm. |
There was a problem hiding this comment.
Was drafting this new limitation to clarify how the requirement status doesn't get updated after an upstream update check in 1.125.2 and earlier:
- For installations using KOTS 1.125.2 or earlier, if you disable the Prevent this release from being skipped during upgrades option for a promoted release, the release will still be marked as required in the Admin Console.
Wasn't sure if there is some sort of workaround in this case (ie, the status doesn't change in the Admin Console but you can skip the previously required version if you upgrade from the CLI or something), or if you'd just need to upgrade to KOTS 1.126.0.
There was a problem hiding this comment.
you'd have to upgrade to KOTS. once KOTS knows about a version, it never processes it again. so it'll say, oh i know about netbox 1.2.3, and i know it's required, so you have to deploy it. and netbox can change that upstream, but kots will never change. (until now of course.)
There was a problem hiding this comment.
Gotcha. I'll add one more sentence to make sure that's clear
paigecalvert
changed the title
https://deploy-preview-3507--replicated-docs.netlify.app/vendor/releases-about#release-properties