Litmus helps SREs and developers practice chaos engineering in a Cloud-native way. Chaos experiments are published at the ChaosHub (https://hub.litmuschaos.io). Community notes is at https://hackmd.io/a4Zu_sH4TZGeih-xCimi3Q
Litmus installed on OpenShift 4.9 with offline registry
We used the ImageContentSourcePolicy to provide a mirror for docker.io/litmuschaos -repositorys (example below)
OpenShift-Nodes still try to pull from docker.io, because the mirror is only used when the image version is provided with digest (mirror-by-digest-only: example below)
Pods fail with ImagePullBackOff
Image gets only pulled when is provided with the digest (instead of tags like „latest“ or similar) because of default registry mirror behaviour in OpenShift
What you expected to happen:
Images pulled from container-registry.internal instead of docker.io
Where can this issue be corrected? (optional)
Helm and YAML-Files should provide image-Digest instead of version-tags.
Example:
docker.io/litmuschaos/litmusportal-frontend:latest = docker.io/litmuschaos/litmusportal-frontend@sha256:aaaaaa
How to reproduce it (as minimally and precisely as possible):
Ensure docker.io is not reachable
Apply the attached Configs to your OpenShift Cluster
What happened:
What you expected to happen: Images pulled from container-registry.internal instead of docker.io
Where can this issue be corrected? (optional) Helm and YAML-Files should provide image-Digest instead of version-tags. Example: docker.io/litmuschaos/litmusportal-frontend:latest = docker.io/litmuschaos/litmusportal-frontend@sha256:aaaaaa
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?: