diff options
| author | k8s-ci-robot <k8s-ci-robot@users.noreply.github.com> | 2018-06-02 13:30:53 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2018-06-02 13:30:53 -0700 |
| commit | 20440305cc969173d9651d37d201da41868a3084 (patch) | |
| tree | 10eea23c09cbcaedcd27fa40ec859b71553a9d02 | |
| parent | 2a5fe97c01551a9ef63c52cee842f59a9346b47f (diff) | |
| parent | b1fb89cc5cdc5bdfbd13ff205b8ea659e71c7eb7 (diff) | |
Merge pull request #2207 from AdamDang/patch-12
Typo fix: A users-> A user
| -rw-r--r-- | contributors/design-proposals/apps/statefulset-update.md | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/contributors/design-proposals/apps/statefulset-update.md b/contributors/design-proposals/apps/statefulset-update.md index 27d3000f..b4089011 100644 --- a/contributors/design-proposals/apps/statefulset-update.md +++ b/contributors/design-proposals/apps/statefulset-update.md @@ -747,7 +747,7 @@ kubectl rollout undo statefulset web ### Rolling Forward Rolling back is usually the safest, and often the fastest, strategy to mitigate deployment failure, but rolling forward is sometimes the only practical solution -for stateful applications (e.g. A users has a minor configuration error but has +for stateful applications (e.g. A user has a minor configuration error but has already modified the storage format for the application). Users can use sequential `kubectl apply`'s to update the StatefulSet's current [target state](#target-state). The StatefulSet's `.Spec.GenerationPartition` |