Why is argo workflow not working in managed K8s?

kubectl create ns argo
kubectl apply -n argo -f

My pods that are started with Argo Workflow are stuck in NotReady state and Argo Workflow shows them as running.

When using k9s to see the logs I see the following:

wait time="2021-04-22T15:41:03.253Z" level=info msg="docker ps --all --no-trunc --format={{.Status}}|{{.Label \"\"}}|{{.ID}}|{{.CreatedAt}} --filter=label=io.kubernetes.pod.namespace=argo"
wait time="2021-04-22T15:41:04.519Z" level=info msg="docker ps --all --no-trunc --format={{.Status}}|{{.Label \"\"}}|{{.ID}}|{{.CreatedAt}} --filter=label=io.kubernetes.pod.namespace=argo"
wait time="2021-04-22T15:41:05.699Z" level=info msg="docker ps --all --no-trunc --format={{.Status}}|{{.Label \"\"}}|{{.ID}}|{{.CreatedAt}} --filter=label=io.kubernetes.pod.namespace=argo"
wait time="2021-04-22T15:41:06.859Z" level=info msg="docker ps --all --no-trunc --format={{.Status}}|{{.Label \"\"}}|{{.ID}}|{{.CreatedAt}} --filter=label=io.kubernetes.pod.namespace=argo"

I gave argo and argo server admin role so it’s probably not related to the permissions.


This comment has been deleted

Submit an answer
You can type!ref in this text area to quickly search our full set of tutorials, documentation & marketplace offerings and insert the link!

These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.

Finally managed to find a solution.

You can --set controller.containerRuntimeExecutor=kubelet and it will work!