docs(faq): add note about pods patch error
#13041
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
- questions about `pods` `patch` errors are probably the most common questions we field on Slack & GH Issues + Discussions, especially by beginners
- so I think this deserves a spot on the FAQ
- users also often only see the error and miss the preceding log that this is a fallback when `workflowtaskresults` RBAC is not available
- so they end up searching the `pod` `patch` error instead, which isn't written about in the docs -- hence this PR
- replace the previous note about "unknown (get pods)", which was removed in v3.3.1 in af26ff7
- also remove the blog link as has dated RBAC and we shouldn't be linking to dated material when possible
- I also left a comment on the blog post clarifying that it's dated: https://medium.com/@agilgur5/note-that-this-blog-post-is-from-oct-2020-cf4cb541915d
Signed-off-by: Anton Gilgur <[email protected]>
juliev0
approved these changes
May 13, 2024
agilgur5
added a commit
that referenced
this pull request
May 14, 2024
- fixed merge conflict with executors note which still exists in 3.5 Signed-off-by: Anton Gilgur <[email protected]> (cherry picked from commit 0bfaea6)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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
podspatcherrors 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, etcworkflowtaskresultsRBAC is not availablepodpatcherror instead, which isn't written about in the docs -- hence this PRModifications
get podsfrom Emissary #8133Verification
make docspassesFuture Work
patchpodsfallback #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