Cloud Native Night, April 2018, Munich: Talk by Sebastian Scheele (@hrscheele, CEO & co-founder of Loodse GmbH) Join our Meetup: https://www.meetup.com/de-DE/cloud-native-muc Abstract: Imagine a world in which a Kubernetes control plane could govern and control node infrastructure in Kubernetes. In this talk, Sebastian will take the user on an adventurous journey through the Kubernetes API and into the infrastructure layer of the stack. Sebastian will introduce the idea of Machine API, talk about the patterns behind declarative nodes and look at the role of the cloud provider within these patterns. The participants will learn how the project integrates cleanly and effortlessly with the Kubernetes API and works out of the box with kubectl. Also, Sebastian will present the work of the official Cluster API effort and the concept of bring-your-own-node-controller.

1. K8s ClusterAPIManaging Kubernetes Cluster

2. Sebastian Scheele
CEO & Co-Founder
Twitter: @hrscheele

3. Company:
Focus:
Product:
Headquarter:
Partner:
Loodse

5. Currently Supported Providers
Bare Metal

6. Node Deployment Solution

7. Current approach
• Need Ops to scale the cluster
• No generic approach
• Each implementation needs
specific knowledge
• Scaling of new nodes requires
external dependencies
• No generic node auto scaling
• Huge effort to deploy k8s on a
different platform
Node Node Node
Master
Node

8. Similar ideas at the same time
Kubicorn
https://github.com/kubicorn/kubicorn
Kube-node
https://github.com/kube-node
Archon
https://github.com/kubeup/archon

9. PersistentVolumes
A higher-level storage abstraction
• insulation from the resource provider
Admins provision them, users claim them
Can be dynamically created using a StorageClass
Independent lifetime from their consumers
Dynamically “scheduled” and managed
Pod
Claim

10. Cluster API

11. Cluster API Repos
In migration
https://github.com/kubernetes/kube-deploy
New repo
https://github.com/kubernetes-sigs/cluster-api

12. Native integration
• Dev can scale the cluster
• Pets vs cattle for nodes
• Implementation of generic auto
scaling possible
• Very similar setup for different
provider
kubectl create machines
Node Node Node
Master
Node

13. Machines/Nodes
• A "Machine" is the declarative spec for a Node,
as represented in Kubernetes core.
• After provisioning a new Node matching the
Machine spec is registered.

14. MachineController
Watches for new Machine resources
Provision the machine using provider-specific drivers
• Machine joins the cluster
• Kubelet creates the Node resource
Machine
Resources

15. MachineClass (Optional)
Encapsulate Cloud Provider & OS specific details
Spec
• Cloud Provider credentials
• Machine type (e.g. t2.medium)
• Provisioning Details
• Files (i.e. systemd unit, ssh keys)
• Execute arbitrary commands via ssh
Machine
Resources
Class

16. MachineSet
Group of similar nodes
Integrates with node autoscaler
Spec:
• Replicas (number of nodes)
• MachineController
• MachineClass Machi
ne
Class
Machi
ne
Machi
ne

17. MachineSetController
Machi
ne
Class
Machi
ne
Machi
ne
Create and delete node resources
Ensures {Cluster Nodes} ==
machineset.replicas

18. Reliable mechanism for creating, updating
and managing Machines
Deployment manages replica changes,
including rolling updates and scaling
...

19. DEMO
TIME

20. Questions?

21. Early Bird
until April 30
20% with
CDS2018_COMMUNITY