From 2691ac23f62b4ed5d0aea1bc461d2bd9ad4340c5 Mon Sep 17 00:00:00 2001 From: Grace Nguyen <42276283+gracenng@users.noreply.github.com> Date: Tue, 22 Aug 2023 10:07:48 -0400 Subject: [PATCH] Corrections edit Co-authored-by: Tim Bannister --- content/en/blog/_posts/2023-08-15-kubernetes-1.28-blog.md | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2023-08-15-kubernetes-1.28-blog.md b/content/en/blog/_posts/2023-08-15-kubernetes-1.28-blog.md index dc57eb6f6c..19519f9f80 100644 --- a/content/en/blog/_posts/2023-08-15-kubernetes-1.28-blog.md +++ b/content/en/blog/_posts/2023-08-15-kubernetes-1.28-blog.md @@ -222,7 +222,8 @@ For instance, if indexed jobs were used as the basis for a suite of long-running For more information, read [Handling Pod and container failures](/docs/concepts/workloads/controllers/job/#handling-pod-and-container-failures) in the Kubernetes documentation. -*Corrections*: the feature CRI container and pod statistics without cAdvisor has been removed as it did not make the release. +**Correction**: the feature CRI container and pod statistics without cAdvisor has been removed as it did not make the release. +The original release announcement stated that Kubernetes 1.28 included the new feature. ## Feature graduations and deprecations in Kubernetes v1.28 ### Graduations to stable