You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
In order to make OLMv1 more than just a toy project upstream, we need to put effort into making it actually upgradeable in upstream Kubernetes clusters.
At a minimum, this would entail:
Documentation that lists valid upgrade paths
Testing, that provides confidence for making changes that will not break upgrades (and perhaps that could even report valid upgrade edges automatically)
A release process that makes new releases available in a consumable and consistent way.
If I'm dreaming big, I think this could look like:
We design and deliver the following as prerequisites:
We start shipping an FBC catalog for OLMv1, containing edges verified by our upgrade tests
We implement an installer that can bootstrap an OLMv1 release into a ClusterExtension
We update our upgrade tests to use the bootstrapping mechanism so that we can reuse all of the existing pre-flight checks and health checking built into OLMv1.
The text was updated successfully, but these errors were encountered:
In order to make OLMv1 more than just a toy project upstream, we need to put effort into making it actually upgradeable in upstream Kubernetes clusters.
At a minimum, this would entail:
If I'm dreaming big, I think this could look like:
ClusterExtension
The text was updated successfully, but these errors were encountered: