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
This issue should be closed when a demo recording is posted to the #olm-dev kubernetes slack channel that follows the below script:
Demo Script:
Install operator-controller from the main branch or its most recently tagged release using operator-controller's standard install script and manifest.
Create a Catalog object referencing quay.io/operatorhubio/catalog:latest
Show that the catalog status reflects that it was successfully unpacked.
Create an Operator object referencing package strimzi-kafka-operator with channel strimzi-0.32.x
Show that a BundleDeployment gets created and references the bundle image quay.io/operatorhubio/strimzi-kafka-operator@sha256:0d4ac0ed10d815b30dca6521d3ceab5dfc150cddda22e9ca83e97462dbcfeff4
Edit the Operator object and change the channel to strimzi-0.33.x
Show that the existing BundleDeployment is updated to reflect a new bundle image reference with quay.io/operatorhubio/strimzi-kafka-operator@sha256:4d953d5fd719ea61a7009daaa7e37c948073132f231c2d2d1b07bf3d0d5d6e3b
Edit the Operator object and remove the channel specification.
Show that the existing BundleDeployment is updated to reflect a new bundle image reference with the highest semver bundle defined in the package (as of 4/5/23, that version is 0.34.0): quay.io/operatorhubio/strimzi-kafka-operator@sha256:42a3dce711492fae22f2d919299a0594f152396f6c2fef65ffc47226ba9c786e
Edit the Operator object and set the channel to foobar.
Show the the Operator object has its status updated to reflect that no version is available in the specified channel. Also show that the BundleDeployment is still present and remains at version 0.34.0.
The text was updated successfully, but these errors were encountered:
joelanford
changed the title
Milestone 4 Goal 1 - Honoring an optional spec.channel field in the Operator API.
Honoring an optional spec.channel field in the Operator API.
Apr 11, 2023
I know perhaps it's wrong place to ask the question, but let me ask anyway: What is the semantics in OLM v1 of the channel concept, in relation to OLM v0?
@pgodowski - can you start a discussion topic for that question? In general the concept is the same, but the mechanics are up for re-evaluation in OLMv1. I suspect we'll need to dive down into specific aspects of what you're trying to understand.
This issue should be closed when a demo recording is posted to the #olm-dev kubernetes slack channel that follows the below script:
Demo Script:
Catalog
object referencingquay.io/operatorhubio/catalog:latest
Operator
object referencing packagestrimzi-kafka-operator
with channelstrimzi-0.32.x
BundleDeployment
gets created and references the bundle imagequay.io/operatorhubio/strimzi-kafka-operator@sha256:0d4ac0ed10d815b30dca6521d3ceab5dfc150cddda22e9ca83e97462dbcfeff4
Operator
object and change the channel tostrimzi-0.33.x
BundleDeployment
is updated to reflect a new bundle image reference withquay.io/operatorhubio/strimzi-kafka-operator@sha256:4d953d5fd719ea61a7009daaa7e37c948073132f231c2d2d1b07bf3d0d5d6e3b
Operator
object and remove the channel specification.BundleDeployment
is updated to reflect a new bundle image reference with the highest semver bundle defined in the package (as of 4/5/23, that version is 0.34.0):quay.io/operatorhubio/strimzi-kafka-operator@sha256:42a3dce711492fae22f2d919299a0594f152396f6c2fef65ffc47226ba9c786e
Operator
object and set the channel tofoobar
.Operator
object has its status updated to reflect that no version is available in the specified channel. Also show that theBundleDeployment
is still present and remains at version 0.34.0.Operator
objects.Related Issues:
The text was updated successfully, but these errors were encountered: