Skip to content

Commit 25a7c8f

Browse files
Update content/en/blog/_posts/2021-08-13-SIG-Node-Spotlight/index.md
Co-authored-by: Rey Lejano <[email protected]>
1 parent 2b09e53 commit 25a7c8f

File tree

1 file changed

+0
-2
lines changed
  • content/en/blog/_posts/2021-08-13-SIG-Node-Spotlight

1 file changed

+0
-2
lines changed

content/en/blog/_posts/2021-08-13-SIG-Node-Spotlight/index.md

Lines changed: 0 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,6 @@ Are you interested in learning about what [SIG Node](https://github.com/kubernet
1818

1919
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.
2020

21-
22-
2321
### "SIG Node is a vertical SIG" could you explain a bit more?
2422

2523
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.

0 commit comments

Comments
 (0)