Issue: Project will always be out of sync, due to chicken egg problem with image streams in Openshift.
Question: Would it be possible to add a section to the course about how to ignore sections of the config that are irrelevant and cause chicken-egg problem?
Details
In Argocd, the config is synced from the git and applied to the cluster. In Openshift there is an option to use image streams which changes the config that is applied to the cluster.
https://docs.okd.io/latest/openshift_images/image-streams-manage.html
When using an image stream:
apiVersion: image.openshift.io/v1
kind: ImageStream
metadata:
name: some-imagestream-that-is-used
then you have in the git repository for the image (There are more lines needed to make it work in Openshift):
containers:
name: some-service-using-image-stream
image: ''
this makes Argocd always to be out of sync since in the cluster, the “” will be replaced with the path to the latest image from the image stream made by Openshift once the config is synced.
To get around this issue, we could ignore the image: ‘’ tag, since we always know it will be out of sync, and probably we could add some own custom health checks with LUA to make sure that there is an image from the image stream.
argo-cd.readthedocs.io/en/stable/user-guide/diffing/
Would it be possible for kodekloud to add some hints or a lab to the course of how to ignore different things in the config?