docs(faq): add note about pods
patch
error
#13041
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Motivation
questions about
pods
patch
errors are probably the most common questions we field on Slack & GH Issues + Discussions, especially by beginnerslinks:
User "system:serviceaccount:argo:default" cannot patch resource "pods" in API group "" in the namespace "argo"
#12783, quick start fails out of the box due to RBAC error #12391, RBAC error when following Quick Start #12398, [archived] "Hello World" docs discussion #12767 (comment), en/latest/walk-through/output-parameters/ #9476 (comment), en/latest/walk-through/output-parameters/ #9476 (comment), [archived] "Loops Walk Through" docs discussion #9478 (comment), [archived] "Container Set Template" docs discussion #10552 (comment), [archived] "Scripts and Results" docs discussion #10570 (comment), [archived] "Recursion" docs discussion #9963 (comment), Slack 1, 2, 3, 4, 5, etc, etc, etcworkflowtaskresults
RBAC is not availablepod
patch
error instead, which isn't written about in the docs -- hence this PRModifications
get pods
from Emissary #8133Verification
make docs
passesFuture Work
We may want to modify this or add to it in the next minor when #12976 lands. I would probably suggest adding a second error message similar to the
"token not valid"
error message above, which has old variants and new variants