-
Notifications
You must be signed in to change notification settings - Fork 333
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
GA roadmap: Incident management and troubleshooting guides #854
Comments
I had a chat with @pjbgf about this and we came to the conclusion that starting with a "troubleshooting cheatsheet" could be a good start. The next step could be a more general doc, including a flow diagram, some more background info, etc does that make sense? here's a quick draft (needs more text still): https://docs.google.com/document/d/1FV4adriWQIH-0JZXeknZhKlPbxa8SibrRcX6SVhgOaQ/edit# |
I like what's already in that doc. Thanks @dholbach. From my point of view we can just start with the items in there and extend the troubleshooting guide/runbook going forward. |
We may want to move over some items from the FAQ, e.g. https://fluxcd.io/docs/faq/#how-do-i-resolve-webhook-does-not-support-dry-run-errors |
https://fluxcd.io/docs/cheatsheets/troubleshooting/ was landed in #1033 We discussed in the 2022-07-20 meeting to ask the community in the next monthly update for feedback on what they feel they'd need to feel well set up for incident management and troubleshooting - or what they use internally e.g. playbooks, etc |
The current documentation on this front suffices for GA, from now on it will be an on-going effort to keep it up to date and improve it. Closing as per #1094 (comment). |
From https://fluxcd.io/roadmap/
Let's discuss "Incident management and troubleshooting guides" - what do we want to add to our docs to be able to resolve this issue?
The text was updated successfully, but these errors were encountered: