From 98ca459e15f62d5661f7f812ad31fc40f4e1ed69 Mon Sep 17 00:00:00 2001 From: "Kiran (they/them)" Date: Wed, 27 May 2020 16:09:45 -0500 Subject: [PATCH] Update content/en/blog/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md Co-authored-by: Taylor Dolezal --- ...7-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/content/en/blog/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md b/content/en/blog/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md index 0858966346..20448e4ff4 100644 --- a/content/en/blog/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md +++ b/content/en/blog/_posts/2020-05-27-An-Introduction-to-the-K8s-Infrastructure-Working-Group.md @@ -15,7 +15,7 @@ A group of community members enthusiastically undertook the task of collaboratin ## What Issues Does the K8s-Infrastructure Working Group Tackle? -The team took on the complex task of managing the many moving parts of infrastructure that sustain Kubernetes as a project. +The team took on the complex task of managing the many moving parts of the infrastructure that sustains Kubernetes as a project. The need started with necessity: the first problem they took on was a complete migration of all of the project's infrastructure from Google-owned infrastructure to the Cloud Native Computing Foundation (CNCF). This is being done so that the project is self-sustainable without the need of any direct assistance from individual vendors. This breaks down in the following ways: