New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
How to solve problem with chaos-runner image? #4587
Comments
hi, can you re-upload the third image? |
Hi, Attached is a screenshot in which you can see the error when obtaining the chaos-runner image. The error is caused because the value of "Image secret" is not being taken. I take this opportunity to attach the values.yaml file that I use in the installation. ` nameOverride: "" customLabels: {} existingSecret: "" adminConfig: image: imagePullSecrets: ingress:
tls: ingressClassName: "chaos-nginx-ingress-controller"
upgradeAgent: portal:
server:
openshift: mongodb: livenessProbe: enabled: true |
@Alan-Vlc , Please add docker secret to your Service account (litmus-admin).
|
Good morning,
The experiment is launched but at the time of downloading the chaos-runner:3.5.1 image I encounter a 401 error when downloading the image.
I have tried downloading the image locally and everything works correctly, however I cannot get the runner pod to include the "Image Secret" from my custom image registry.
The rest of the images are correctly obtained from my custom image registry with the corresponding "Image secret". I have checked that in the values with which I carried out the installation, the value of imageRegistryName and imagePullSecrets is correctly specified.
How can I solve this issue?
The text was updated successfully, but these errors were encountered: