litmuschaos / litmus

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
https://litmuschaos.io
Apache License 2.0
4.44k stars 698 forks source link

How to solve problem with chaos-runner image? #4587

Open Alan-Vlc opened 7 months ago

Alan-Vlc commented 7 months ago

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.

image

image

image

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?

namkyu1999 commented 7 months ago

hi, can you re-upload the third image?

Alan-Vlc commented 7 months ago

Hi,

Attached is a screenshot in which you can see the error when obtaining the chaos-runner image.

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.

` portalScope: cluster

nameOverride: ""

customLabels: {}

existingSecret: ""

adminConfig: JWTSecret: "litmus-portal@123" VERSION: "3.5.0" SKIP_SSL_VERIFY: "false" DBPASSWORD: "" DBUSER: "" DB_SERVER: "" DB_PORT: "" ADMIN_USERNAME: "*" ADMIN_PASSWORD: "***"

image: imageRegistryName: docker.artifactory.gcp.***.com

imagePullSecrets:

ingress: enabled: true name: litmus-ingress annotations:

 nginx.ingress.kubernetes.io/rewrite-target: /$1

tls:

upgradeAgent: enabled: true controlPlane: image: repository: litmuschaos/upgrade-agent-cp tag: "3.5.0" pullPolicy: "Always" restartPolicy: OnFailure nodeSelector: {} tolerations: [] affinity: {} resources: {}

portal: frontend: replicas: 1 autoscaling: enabled: false minReplicas: 2 maxReplicas: 3 targetCPUUtilizationPercentage: 50 targetMemoryUtilizationPercentage: 50 updateStrategy: {}

image:
  repository: litmuschaos/litmusportal-frontend
  tag: 3.5.0
  pullPolicy: "Always"
containerPort: 8185
customLabels: {}

resources:
  requests:
    memory: "150Mi"
    cpu: "125m"
    ephemeral-storage: "500Mi"
  limits:
    memory: "512Mi"
    cpu: "550m"
    ephemeral-storage: "1Gi"
livenessProbe:
  failureThreshold: 5
  initialDelaySeconds: 30
  periodSeconds: 10
  successThreshold: 1
  timeoutSeconds: 5
readinessProbe:
  initialDelaySeconds: 5
  periodSeconds: 10
  successThreshold: 1
  timeoutSeconds: 1
service:
  annotations: {}
  type: ClusterIP
  port: 9091
  targetPort: 8185
virtualService:
  enabled: false
  hosts: []
  gateways: []
  pathPrefixEnabled: false
nodeSelector: {}
tolerations: []
affinity: {}

server: replicas: 1 updateStrategy: {} serviceAccountName: litmus-server-account customLabels: {} waitForMongodb: image: repository: mongo tag: latest pullPolicy: "Always" securityContext: {} resources: requests: memory: "150Mi" cpu: "25m" ephemeral-storage: "500Mi" limits: memory: "512Mi" cpu: "250m" ephemeral-storage: "1Gi" graphqlServer: volumes:

openshift: route: enabled: false name: litmus-portal customLabels: {} annotations: {} host: ""

mongodb:

livenessProbe: timeoutSeconds: 20 readinessProbe: timeoutSeconds: 20

enabled: true auth: enabled: true rootUser: "root" rootPassword: "***" existingSecret: "" architecture: standalone replicaCount: 1 persistence: enabled: true volumePermissions: enabled: true metrics: enabled: false prometheusRule: enabled: false

Devendranathashok commented 6 months ago

@Alan-Vlc , Please add docker secret to your Service account (litmus-admin). ex: kind: ServiceAccount apiVersion: v1 metadata: name: litmus-admin namespace: litmus labels: name: litmus-admin imagePullSecrets: