Hi Ted! My main concern here is how do we ensure that the bundle uploaded to the OLM registry is vetted by the community and corresponds to the latest release.
I think we definitely should not upload anything until the release process is complete and the community actually tested the bundle. So my question is, is it possible to test the OLM bundle if we simply tar it like the helm / source release and put it in the staging repo? If so then we should test it from there, and once the release is approved, uploading to the OLM repo should be a similar finalization step as to uploading the docker containers to Dockerhub. Cheers, Gyula On Mon, Nov 21, 2022 at 6:54 PM Hao t Chang <htch...@us.ibm.com> wrote: > Hi Gyula, > > We will let you decide the bundle should be an artifact or not. In my > opinion, the easiest way people may test the bundle is that the catalog and > bundle images are already in a registry. This way, people only need to > apply the catsrc, og, and sub( > https://github.com/tedhtchang/olm/blob/5e147d6223c0056b87f26f55e24d14aac37ed12a/AutomatedOLMBuildAndDeploy.sh#L18-L60) > to install the operator. They don’t really touch the bundle files unless > they are going to modify the bundle. > > -- > Best, > Ted Chang | Software Engineer | htch...@us.ibm.com > > >
