diff options
| author | John Belamaric <jbelamaric@google.com> | 2020-02-19 10:12:58 -0800 |
|---|---|---|
| committer | John Belamaric <jbelamaric@google.com> | 2020-02-19 10:12:58 -0800 |
| commit | fd86a5d6d009c0325716e6aff61ff4a61d570fa7 (patch) | |
| tree | d4b28f2e32a9f935e4441cfd7e58b6091cb498fd | |
| parent | fb1dc03fc0db7c93747078a8cda4100b47c0a90e (diff) | |
Add clarification for PRR troublshooting question
| -rw-r--r-- | sig-architecture/production-readiness.md | 2 |
1 files changed, 2 insertions, 0 deletions
diff --git a/sig-architecture/production-readiness.md b/sig-architecture/production-readiness.md index 28332601..43e74074 100644 --- a/sig-architecture/production-readiness.md +++ b/sig-architecture/production-readiness.md @@ -133,6 +133,8 @@ further stages (e.g. Beta/Ga) of feature lifecycle. * **What are other known failure modes?** * **How can those be detected via metrics or logs?** + Stated another way: how can an operator troubleshoot without logging into a + master or worker node? * **What are the mitigations for each of those failure modes?** |