<!---
This is an autogenerated file!

Please do not edit this file directly, but instead make changes to the
sigs.yaml file in the project root.

To understand how this file is generated, see generator/README.md.
-->
# Node SIG


## Meetings
* [Tuesdays at 17:00 UTC](https://plus.google.com/hangouts/_/google.com/sig-node-meetup?authuser=0) (weekly). [Convert to your timezone](http://www.thetimezoneconverter.com/?t=17:00&tz=UTC).

Meeting notes and Agenda can be found [here](https://docs.google.com/document/d/1Ne57gvidMEWXR70OxxnRkYquAoMpt56o75oZtg-OeBg/edit?usp=sharing).

## Leads
* [Dawn Chen](https://github.com/dchen1107), Google
* [Derek Carr](https://github.com/derekwaynecarr), Red Hat

## Contact
* [Slack](https://kubernetes.slack.com/messages/sig-node)
* [Mailing list](https://groups.google.com/forum/#!forum/kubernetes-sig-node)

<!-- BEGIN CUSTOM CONTENT -->
## Goals

Topics include, but are not limited to:

* Kubelet related features (e.g. Pod lifecycle)
* Node level performance and scalability (with [sig-scalability](../sig-scalability))
* Node reliability
* Node lifecycle management (with [sig-cluster-lifecycle](../sig-cluster-lifecycle))
* Container runtimes: docker, [rkt](../sig-rktnetes), etc.
* Images, package management
* Resource management (with [sig-scheduling](../sig-scheduling))
* Issues related to monitoring (with [sig-instrumentation](../sig-instrumentation))
* Node level security and Pod isolation (with [sig-auth](../sig-auth))
* Kernel interactions (to a limited extent)
* ...

We also work closely with [sig-storage](../sig-storage) and [sig-networking](../sig-networking). As you can see, this is a very cross-functional team!
<!-- END CUSTOM CONTENT -->
