From 7d9ccbc6667ae14af1c2d04691ce9c50b0507ef9 Mon Sep 17 00:00:00 2001 From: Jordan Liggitt Date: Tue, 4 Apr 2023 13:31:59 -0400 Subject: [PATCH] Fix header casing --- .../en/blog/_posts/2023-04-14-improving-support-go-updates.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/blog/_posts/2023-04-14-improving-support-go-updates.md b/content/en/blog/_posts/2023-04-14-improving-support-go-updates.md index d55b03c7494..3579d58843b 100644 --- a/content/en/blog/_posts/2023-04-14-improving-support-go-updates.md +++ b/content/en/blog/_posts/2023-04-14-improving-support-go-updates.md @@ -7,7 +7,7 @@ slug: improving-support-go-updates **Author**: [Jordan Liggitt](https://github.com/liggitt) (Google) -### The Problem +### The problem Since v1.19 (released in 2020), the Kubernetes project provides 12-14 months of patch releases for each minor version. This enables users to qualify and adopt Kubernetes versions in an annual upgrade cycle and receive security fixes for a year. @@ -43,7 +43,7 @@ users would have to upgrade away from older Kubernetes minor versions before the If a user was not prepared to do that upgrade, it could result in vulnerable Kubernetes clusters. Even if a user could accommodate the unexpected upgrade, the uncertainty made Kubernetes' annual support less reliable for planning. -### The Solution +### The solution We're happy to announce that the gap between supported Kubernetes versions and supported Go versions has been resolved as of January 2023.