diff options
| -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` |