J0zi

Thanks @camilamacedo86 for steering it

@rashmigottipati https://github.com/operator-framework/operator-sdk/issues/5616 was not fixed. Still struggling to upgrade ``` operator-sdk run bundle quay.io/community-operators-pipeline/flux:v0.25.2 operator-sdk run bundle-upgrade quay.io/operator_testing/flux:testing0.25.3 ``` or ``` operator-sdk run bundle quay.io/community-operators-pipeline/apicurito:v1.0.2 operator-sdk run bundle-upgrade quay.io/operator_testing/apicurito:testing-apicurito.v1.0.3 ```...

So we are waiting for another release of `operator-sdk` to test it out and we could be unblocked then.

@gallettilance @dinhxuanvu it not only blocks new categories to be added but we are unable to use the latest `opm`/`operator-sdk` in our pipelines. We are running `operator-sdk` in container which...

we found `-b none` working for sdk :tada: Need to test it more.

Despite `-b none` works in case of sdk against quay registry, issue still persist accessing local kind registry from a container.

We can confirm, that `-b podman` was working in very old version `0.18.2` but now not working at all. We are executing an sdk command on a container against local...

+1

@joelanford It would be perfect for user to enter just bundle path and leave tricks for `opm` to handle image path string to the correct line. What do you think?

@joelanford `opm render --link-to-bundle=` could render from directory and add only following stanza: ``` relatedImages: - image: quay.io/openshift-community-operators/sosreport-operator:v0.0.2 name: "" ``` So it is adding missing puzzle there, path to...