Provide a stable subscription channel
Deployment automation may be long-lived, especially for one-click workshop deployments and similar use cases. As such, the operator should provide subscription channels that will be stable over time (i.e., they'll exist and be pinned to compatible versions). By "stable," I do not mean that the contents of the channel include only "stable" software, just that the channels will exist and provide a version of ODH that will deploy on current versions of OCP.
The automation for our Summit labs (last week) installed ODH 0.5.1 from the
alpha channel; the automation for our IBM Think labs (this week) failed to install ODH because the
alpha channel no longer exists as of 417317d3.
As a developer of content that depends on ODH, I want (1) operator subscription channel names to continue to exist over time (perhaps with a deprecation period if they must be deleted) and (2) a subscription channel that refers to some version of ODH suitable for reproducible workshops (i.e., whatever version we're deploying for RHTE or Summit in a given year). Ideally the "workshop channel" would be stable long-term for workshop deployments, but keeping it consistent between, e.g., code freezes for annual Summit events would limit the impact of changes.