Conversation
samiura
force-pushed
the
update-helm-operator-version-to-413
branch
30 times, most recently
from
f27db33 to
0246534
Compare
…c images instead of ghcr registry ones
| newName: ghcr.io/samiura/sumologic-kubernetes-collection-helm-operator | ||
| newTag: 4.13.0 | ||
| newName: registry.connect.redhat.com/sumologic/sumologic-kubernetes-collection-helm-operator | ||
| newTag: 4.9.0-3 |
There was a problem hiding this comment.
When does this tag get updated to the latest?
There was a problem hiding this comment.
@rnishtala-sumo After you have the image ready ( Helm Operator image ). You can update this with having the helm operator image or it will fail. This should be updated as soon as you have the release candidate image ready and then do the catalog test.
|
LGTM! thanks for getting to the bottom of this. We can now run some local and E2E tests on this RC before the final release. |
|
@rnishtala-sumo once we have RC image, we will first do ,1) Catalog tests and 2) local e2e tests to see metrics flowing to our backend before moving to final steps 1) certification of operator image , 2 ) PRS to marketplace and Red Hat Certified operator repository. |
3 participants
Updated all operator component images with the latest certified images.
For verification of the image digests, we can use https://connect.redhat.com/manage/products/6075d88c2b962feb86bea730/components