-
Notifications
You must be signed in to change notification settings - Fork 3.2k
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
Error status for first pod on k3s 1.0.1 #2064
Comments
Can you try and “pns” executor with k3s? |
Worked. Thank you, sir! Since I'm new to argo, could you give brief motivation for why there's a need to have different executors? (Imo, this info would improve the documentation in https://github.com/argoproj/argo/blob/master/docs/workflow-executors.md.) Also, since pns is declared immature and I do not have tight performance requirements, should I use k8sapi instead? Thanks again. PS: For anybody in my situation:
Further info: |
Each executor gives a trade off, with Docker being the most widely supported. I'd note you can run K3S on Docker. |
Hi, after upgrading to argo 2.5rc6 via
I get the following error
I.e., the workflow fails after the first of several steps. Even though logs of the container main show the expected whale. The error message failed to save outputs: Failed to establish pod watch: unknown (get pods) occurs for all executors (docker, kubelet, k8sapi, and pns). Regards. |
Thank you for a good detailed comment. Failing to establish watches maybe caused by the controller not having permission, can you check the getting started guide for this? https://github.com/argoproj/argo/blob/master/docs/getting-started.md You might want to try out the quick-start-*.yaml manifests if you're experimenting. This include all the roles and permissions and are what we use for our testing: https://github.com/argoproj/argo/tree/release-2.5/manifests |
Thanks for the snappy response! As you indicated, the default:default SA did not have sufficient permissions. I ran
and (multi-step) workflows succeed :-) Thank you! |
I just experienced the same issue on GKE |
Checklist:
What happened:
A fresh install of argo (like given in quick start) and submit of the hello world work flow produces an error status with the message.
This is the work flow yaml (copied from git repo):
What you expected to happen:
I expected a success message to appear.
How to reproduce it (as minimally and precisely as possible):
Anything else we need to know?:
kubectl logs <failedpodname> -c init
fails, see below for error message.The container ran successfully:
kubectl logs <failedpodname> -c main
Other example workflows, like e.g. steps or dag-diamond, fail after the first step.
Environment:
Other debugging information (if applicable):
init:
wait:
Logs
Message from the maintainers:
If you are impacted by this bug please add a 👍 reaction to this issue! We often sort issues this way to know what to prioritize.
The text was updated successfully, but these errors were encountered: