Provide alternate image registry to dockerhub about cstor-operators HOT 7 CLOSED

Raised PR in linux-utils to push image to ghcr. cc: @kmova

from cstor-operators.

@anthr76 @dirtycajunrice - just reaching out to check if you would be interested in helping out adding the pushing to ghcr.io.

The steps to push are pretty straightforward and can be seen in this PR. openebs/linux-utils#16

The change need to be pushed to following repos:

• https://github.com/openebs/libcstor/tree/master/.github/workflows
• https://github.com/openebs/istgt/tree/replication/.github/workflows
• https://github.com/openebs/node-disk-manager/tree/master/.github/workflows
• https://github.com/openebs/cstor-operators/tree/master/.github/workflows
• https://github.com/openebs/cstor-csi/tree/master/.github/workflows

from cstor-operators.

@anthr76 from v2.9.0 release onwards, we are again going to push the multi arch images in quay.io (multi arch images not supported earlier).

There were some transisition happening towards github actions in CI/CD and release workflow with multi arch images , which is completed now.

from cstor-operators.

That's great!

from cstor-operators.

Does this include all images? The ones that I currently have deploy are:

openebs/cspc-operator:2.8.0
openebs/cstor-csi-driver:2.8.0
openebs/cstor-istgt:2.8.0
openebs/cstor-pool-manager:2.8.0
openebs/cstor-pool:2.8.0
openebs/cstor-volume-manager:2.8.0
openebs/cstor-webhook:2.8.0
openebs/cvc-operator:2.8.0
openebs/m-exporter:2.8.0
openebs/node-disk-manager:1.4.0
openebs/node-disk-operator:1.4.0

additionally if the images are already going into github ci/cd why would it not also push to ghcr.io? it would be nearly instant

from cstor-operators.

Does this include all images? The ones that I currently have deploy are:

@dirtycajunrice yes, it include all the images. We are yet to decide to push the images in ghcr.io.

from cstor-operators.

Adding to list of to-dos now

from cstor-operators.