-
Story
-
Resolution: Unresolved
-
Major
-
None
-
None
-
Upstream
-
3
-
False
-
None
-
False
-
-
-
NetObserv - Sprint 266, NetObserv - Sprint 267, NetObserv - Sprint 268, NetObserv - Sprint 269
-
Important
With NETOBSERV-2002 we lost info on what version the operator bundle belongs that comes from the bundle tagged as "v0.0.0-main", current labels it produces are:
$ oc image info quay.io/netobserv/network-observability-operator-bundle:v0.0.0-main -o json --filter-by-os linux/amd64 | jq '.config.config' { "Env": [ "PATH=/usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin" ], "WorkingDir": "/", "Labels": { "operators.operatorframework.io.bundle.channel.default.v1": "community", "operators.operatorframework.io.bundle.channels.v1": "latest,community", "operators.operatorframework.io.bundle.manifests.v1": "manifests/", "operators.operatorframework.io.bundle.mediatype.v1": "registry+v1", "operators.operatorframework.io.bundle.metadata.v1": "metadata/", "operators.operatorframework.io.bundle.package.v1": "netobserv-operator", "operators.operatorframework.io.metrics.builder": "operator-sdk-v1.25.3", "operators.operatorframework.io.metrics.mediatype.v1": "metrics+v1", "operators.operatorframework.io.metrics.project_layout": "go.kubebuilder.io/v3", "operators.operatorframework.io.test.config.v1": "tests/scorecard/", "operators.operatorframework.io.test.mediatype.v1": "scorecard+v1" } }
With downstream bundles be it CPASS/konflux this info is available as one of the labels, for e.g: with one of the konflux builds:
$ oc image info quay.io/redhat-user-workloads/ocp-network-observab-tenant/netobserv-operator/network-observability-operator-bundle@sha256:245605651ba28aa3c747d2aa8cff2b16041c59c83b1aaf02e3276753a5d09463 -o json --filter-by-os linux/amd64 | jq '.config.config.Labels.version' "1.8.0"
With CPASS it was even better where along with with version we could extract iteration of the bundle from the URL label of the bundle image for e.g: 1.7.0-98
We should publish version field to operator bundle produced by the main branch that its targeting to ship and if possible iteration of the bundle as well to help keep track of perf runs baselines and regressions.