From 6dc2c52d1374895c0cd4eee6921b61d83e252ed9 Mon Sep 17 00:00:00 2001 From: Dipesh Rawat Date: Tue, 29 Aug 2023 00:04:45 +0100 Subject: [PATCH] Corrected broken link in the blog --- .../en/blog/_posts/2020-08-21-Moving-Forward-From-Beta/index.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2020-08-21-Moving-Forward-From-Beta/index.md b/content/en/blog/_posts/2020-08-21-Moving-Forward-From-Beta/index.md index 1d82e67fb2..d62fb29461 100644 --- a/content/en/blog/_posts/2020-08-21-Moving-Forward-From-Beta/index.md +++ b/content/en/blog/_posts/2020-08-21-Moving-Forward-From-Beta/index.md @@ -12,7 +12,7 @@ In Kubernetes, features follow a defined First, as the twinkle of an eye in an interested developer. Maybe, then, sketched in online discussions, drawn on the online equivalent of a cafe napkin. This rough work typically becomes a -[Kubernetes Enhancement Proposal](https://github.com/kubernetes/enhancements/blob/master/keps/0001-kubernetes-enhancement-proposal-process.md#kubernetes-enhancement-proposal-process) (KEP), and +[Kubernetes Enhancement Proposal](https://github.com/kubernetes/enhancements/blob/master/keps/sig-architecture/0000-kep-process/README.md#kubernetes-enhancement-proposal-process) (KEP), and from there it usually turns into code. For Kubernetes v1.20 and onwards, we're focusing on helping that code