generate bundle and catalog, add release command

[jgbernalp]

This PR creates the missing bundle dockerfile to build a bundle. It also adds a release command that builds and deploys the bundle and catalog

[Nexucis]

Overall it looks fine, I just don't understand what we have to publish.(certainly because I am not familiar with the release and deployment workflow of the operator)

Do we need to publish also a docker image containing the operator binary (a.k.a build thanks to main.go) ?
Or actually it's not necessary and we just need to publish the bundle image ?
Or do we need to publish both ?

Asking that because if we only need to publish the bundle image, I can imagining we don't need goreleaser anymore to be able to build docker manifest for arm64 and amd64

[jgbernalp]

We need 3 images:

• perses-operator: Image with the operator binary, we can use the go releaser as we need multi-arch support.
• bundle: Image with metadata. Contains Perses CRDs, other operator metadata and configuration. It references the perses-operator image, in this case: docker.io/persesdev/[email protected]. These are not architecture specific images, but describe that the perses-operator binary supports multiple archs
• catalog: Image with metadata. Can reference multiple bundles, in this case references the perses bundle: docker.io/persesdev/[email protected]. I will add a specific catalog image dockerfile in another PR, for now is using a default generated image.

[Nexucis]

cool thanks for the explanations @jgbernalp it's clearer now !

[Nexucis]

for the moment, only amd64 and arm64 are supported.

[jgbernalp]

ok will adjust.

[Nexucis]

👍