diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2020-02-19 11:38:28 -0800 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2020-02-19 11:38:28 -0800 |
| commit | 62474707c56cc81c4312baa545eadc8a8b4e972e (patch) | |
| tree | 4814c328201ad0f694d58b9a33b9465978d8c799 | |
| parent | 2ba9e8ee05a03a4dc062bdfc550f8dd954c38b53 (diff) | |
| parent | fd86a5d6d009c0325716e6aff61ff4a61d570fa7 (diff) | |
Merge pull request #4532 from johnbelamaric/prr-refinement
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?** |