Rktnetes: Modular container engines for Kubernetes

Kubernetes 1st birthday party, Work-Bench, NY, NY

Transcript

1. Rktnetes: Modular container engines for Kubernetes Josh Wood DocOps at CoreOS @joshixisjosh9
3. We’re hiring in all departments! Email: careers@coreos.com Positions: coreos.com/ careers 90+ Projects on GitHub, 1,000+ Contributors OPEN SOURCE CoreOS.com - @coreoslinux - github/coreos Secure solutions, support plans, training + more ENTERPRISE sales@coreos.com - tectonic.com - quay.io CoreOS Runs the World’s Containers
4. A CLI for running app containers on Linux. Focuses on: • Security • Composability • Standards/Compatibility
5. What is rktnetes? • “Rktnetes” is a nickname for the work in both rkt and kubernetes • rkt is container execution engine, runs cluster work on nodes • Add configuration switches to declare a node uses the rkt engine, or that a pod executes with rkt
6. What is rktnetes? • Add a rkt api service for read-side API service
7. Why rktnetes? • Ensure cleanliness and modularity of the critical interface between the orchestrator and the execution engine • Spur innovation through community effects
8. Why rktnetes? • Obtain unique rkt features • Externally modular: exercise different interface than Docker API • Internally modular: Pluggable “stage1” isolation environments • Run pods as software-isolated (cgroups, ns) • Run pods as VMs with hypervisor isolation
9. What’s up and what’s next? • Rktnetes is part of mainline Kubernetes v1.3 • Bring up a cluster, node, or pod with rkt as the executor • Next: ◦ kubectl attach ◦ Port-forwarding for alternate stage1s ◦ Your contributions, suggestions, and experiments!
10. See also: • coreos.com/rkt • kubernetes.io/docs/getting-started-guides/rkt/
11. Thank you! Josh Wood @joshixisjosh9 | j@coreos.com | github.com/joshix We’re hiring in NYC! Email: careers@coreos.com Positions: coreos.com/ careers