From 25a7c8f02e76128bdc270475c73123e45810daad Mon Sep 17 00:00:00 2001 From: Dewan Ishtiaque Ahmed <30604461+dewan-ahmed@users.noreply.github.com> Date: Wed, 25 Aug 2021 17:29:05 -0300 Subject: [PATCH] Update content/en/blog/_posts/2021-08-13-SIG-Node-Spotlight/index.md Co-authored-by: Rey Lejano --- content/en/blog/_posts/2021-08-13-SIG-Node-Spotlight/index.md | 2 -- 1 file changed, 2 deletions(-) diff --git a/content/en/blog/_posts/2021-08-13-SIG-Node-Spotlight/index.md b/content/en/blog/_posts/2021-08-13-SIG-Node-Spotlight/index.md index 269b6cc140..8a9b07c514 100644 --- a/content/en/blog/_posts/2021-08-13-SIG-Node-Spotlight/index.md +++ b/content/en/blog/_posts/2021-08-13-SIG-Node-Spotlight/index.md @@ -18,8 +18,6 @@ Are you interested in learning about what [SIG Node](https://github.com/kubernet SK: SIG Node is a vertical SIG responsible for the components that support the controlled interactions between the pods and host resources. We manage the lifecycle of pods that are scheduled to a node. This SIG's focus is to enable a broad set of workload types, including workloads with hardware specific or performance sensitive requirements. All while maintaining isolation boundaries between pods on a node, as well as the pod and the host. This SIG maintains quite a few components and has many external dependencies (like container runtimes or operating system features), which makes the complexity we deal with huge. We tame the complexity and aim to continuously improve node reliability. - - ### "SIG Node is a vertical SIG" could you explain a bit more? EH: There are two kinds of SIGs: horizontal and vertical. Horizontal SIGs are concerned with a particular function of every component in Kubernetes: for example, SIG Security considers security aspects of every component in Kubernetes, or SIG Instrumentation looks at the logs, metrics, traces and events of every component in Kubernetes. Such SIGs don't tend to own a lot of code.