From 5c29ba19c11f8024244c0609496cdf2810a7b0d2 Mon Sep 17 00:00:00 2001 From: Tim Bannister Date: Thu, 26 May 2022 14:17:57 +0100 Subject: [PATCH] Avoid promising future articles on SIG Apps topics --- .../en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md | 1 - 1 file changed, 1 deletion(-) diff --git a/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md b/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md index d61904c80b4..aa6257eb3ef 100644 --- a/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md +++ b/content/en/blog/_posts/2022-05-27-maxunavailable-for-statefulset.md @@ -141,7 +141,6 @@ It might be better to try and see it for yourself. This is an alpha feature, and this help you achieve your stateful scenarios Did you find a bug or do you think the behavior as implemented is not intuitive or can break applications or catch them by surprise? Please [open an issue](https://github.com/kubernetes/kubernetes/issues) to let us know. -Keep an eye on this space, for more blogs to dissect the behavior of this feature in the coming months. ## Further reading and next steps {#next-steps} - [Maximum unavailable Pods](/docs/concepts/workloads/controllers/statefulset/#maximum-unavailable-pods) - [KEP for MaxUnavailable for StatefulSet](https://github.com/kubernetes/enhancements/tree/master/keps/sig-apps/961-maxunavailable-for-statefulset)