-
Story
-
Resolution: Done
-
Normal
-
None
-
None
-
False
-
False
-
Passed
-
Undefined
-
-
Sprint 205
Today, automatic updates typically roll out to a user along the same channel, but if they're using something like MTC 1.3, they are not notified that an MTC 1.4 channel is now available to them.
As a user, I'd like to be alerted in the MTC UI when there is a newer channel that's available to me, because that means a significant release with new features is probably available.
As the dev team, we want to make it more clear to users that these new releases are available, because currently there seems to be a slow adoption of new channels (in particular, 1.4).
We suspect there is some way for our operator to periodically interrogate operator metadata servers so that if a newer, or more preferred channel is available but not installed, it can mark this information in the MigrationController `status`, and then the UI can read from this. If the warning/notification is present, it can notify with a dismissable warning in the UI.
Note longer term solution in OLM is tracked in OLM-2059 Cross-Channel Updates