aws-samples / eks-workshop

AWS Workshop for Learning EKS
https://eksworkshop.com
MIT No Attribution
803 stars 1.24k forks source link

argo-workflow message: 'Internal error occurred: failed calling webhook "mutating.pod-env-webhook.svc" #961

Closed perlinger closed 1 year ago

perlinger commented 4 years ago

After running command below to install argo-workflows kubectl apply -n argo -f https://raw.githubusercontent.com/argoproj/argo/stable/manifests/install.yaml

I ran this command to check on the health of the deployment kubectl get deployment argo-server -n argo -0 yaml And, in the status response was a message with an internal error. How do I fix the error?

kubectl get deployment argo-server -n argo -o yaml apiVersion: extensions/v1beta1 kind: Deployment metadata: annotations: deployment.kubernetes.io/revision: "2" kubectl.kubernetes.io/last-applied-configuration: | {"apiVersion":"apps/v1","kind":"Deployment","metadata":{"annotations":{},"name":"argo-server","namespace":"argo"},"spec":{"selector":{"matchLabels":{"app":"argo-server"}},"template":{"metadata":{"labels":{"app":"argo-server"}},"spec":{"containers":[{"args":["server"],"image":"argoproj/argocli:v2.11.6","name":"argo-server","ports":[{"containerPort":2746,"name":"web"}],"readinessProbe":{"httpGet":{"path":"/","port":2746,"scheme":"HTTP"},"initialDelaySeconds":10,"periodSeconds":20}}],"nodeSelector":{"kubernetes.io/os":"linux"},"serviceAccountName":"argo-server"}}}} creationTimestamp: "2020-10-26T21:34:00Z" generation: 2 name: argo-server namespace: argo resourceVersion: "276522180" selfLink: /apis/extensions/v1beta1/namespaces/argo/deployments/argo-server uid: e6c55fe2-157e-4a53-a77a-6b070f368cd1 spec: progressDeadlineSeconds: 600 replicas: 1 revisionHistoryLimit: 10 selector: matchLabels: app: argo-server strategy: rollingUpdate: maxSurge: 25% maxUnavailable: 25% type: RollingUpdate template: metadata: creationTimestamp: null labels: app: argo-server spec: containers:

github-actions[bot] commented 1 year ago

This issue is stale because it has been open for 30 days with no activity.

github-actions[bot] commented 1 year ago

This issue was closed because it has been inactive for 14 days since being marked as stale.