Update helm chart for OES v3.5 release #96
Conversation
charts/oes/values.yaml
Outdated
| front50.yml: | ||
| artifactId: quay.io/opsmxpublic/ubi8-oes-front50:0.25.1-opa | ||
| artifactId: quay.io/opsmxpublic/ubi8-spin-front50:0.26.1-opa |
There was a problem hiding this comment.
Question: Why did we use the oes front50 earlier? Was it or the OPA policy while saving pipelines and now it is part of the regular spin image?
There was a problem hiding this comment.
My understanding is if we are building the images with the customized changes from our forked repo, they should be pushed to the repo ubi8-oes-<service>:<tag>, and if images are built from open source code without any customizations using ubi8 base image, they should be pushed to the repo ubi8-spin-<service>:<tag>
Correct me if my understanding is wrong.
In this case, I think image was pushed to ubi8-spin-front50 instead of pushing it to ubi8-oes-front50.
There was a problem hiding this comment.
Addressed this, image is now ubi8-oes-front50:0.26.1
No description provided.