Introduction to Virtual Kubelet
2 likes1,577 views
This document introduces Virtual Kubelet, which extends the Kubernetes API to serverless container platforms. It treats the concept of pods and nodes abstractly, allowing pods to run on platforms like ACI and Fargate. Virtual Kubelet implements a provider interface to manage the pod lifecycle on these platforms. It also allows hybrid use cases like running traditional and serverless pods together. The document demonstrates how Virtual Kubelet can schedule pods to ACI from an AKS cluster and to Nomad from a Kubernetes cluster.
Introduction to Virtual Kubelet
- 1. Introduction to Virtual Kubelet Ria Bhatia, Program Manager, Microsoft Anubhav Mishra, Developer Advocate, HashiCorp
- 2. Ria Bhatia Program Manager, Microsoft @rbitia Maintainer of Virtual Kubelet Core
- 3. Anubhav Mishra Team Lead, Developer Advocacy, HashiCorp @anubhavm - Kubernetes Community - Provider Maintainer, Virtual Kubelet - Helm, Secret CSI Driver
- 5. Virtual Kubelet • Open Sourced by Microsoft in 2017 • Extend the Kubernetes API to serverless container platforms like ACI, Fargate, Google Containers.
- 7. A Long Time Ago…..
- 9. Kubernetes Architecture In two slides…..
- 10. 10
- 11. 11
- 12. 12
- 13. Anatomy of a Node • Kubernetes is fundamentally a node-based scheduling system • A node comes with a number of conventions and constraints • Pods are run in the same address space • Pods are executed using low-level operating system primitives (cgroups / namespaces) • Pods share node resources - kernel, ephemeral disk, container images • Pods inherit certain aspects of node configuration • Node is a static size • Privileged containers expect to interact directly with node resources • A node is a single fault domain - affinity consideration
- 14. Anatomy of a Node: Node Agent
- 15. Introduction to Virtual Kubelet • VK treats the concept of pods and nodes in the abstract • A node is a bounded amount of resource • A pod is a set of containers running within a sandbox • The specifics of how these are manifested is contained within a pluggable Provider • Common code in VK is relatively small • Registers with the API server as a client • Polls for state changes in Objects • Reports back state of "node" and "pods" • Handles synchronous interaction with containers • VK can itself be deployed as a Pod
- 16. Why Virtual Kubelet? • Flexibility of abstraction • Flexibility of resource consumption • Greater granularity – pay for pods, not nodes • Hybrid use-case - traditional cluster with a VK node for bursting / batch / on-demand pricing • Single cluster high availability - a VK in each availability zone • IOT edge connector - a VK schedules to a set of IOT devices • Alternate Kubelet – VK as a node agent in a different kind of node
- 17. 17
- 18. Provider Interface EDITOR // Provider contains the methods required to implement a Virtual Kubelet provider type Provider interface { // Takes a Kubernetes Pod and deploys it within the provider CreatePod(ctx context.Context, pod *v1.Pod) error // Takes a Kubernetes Pod and updates it within the provider UpdatePod(ctx context.Context, pod *v1.Pod) error // Takes a Kubernetes Pod and deletes it from the provider DeletePod(ctx context.Context, pod *v1.Pod) error // Retrieves a pod by name from the provider (can be cached) GetPod(ctx context.Context, namespace, name string) (*v1.Pod, error) // Retrieves the logs of a container by name from the provider GetContainerLogs(ctx context.Context, namespace, podName, containerName string, tail int) (string, error) .....
- 19. Provider Definition • Provide the back-end plumbing necessary to support the lifecycle management of pods, containers and supporting resources in the context of Kubernetes. • Conform to the current API provided by Virtual Kubelet. • Not have access to the Kubernetes API Server and has a well- defined callback mechanism for getting data like secrets or configmaps.
- 20. Extend Kubernetes workloads to any service you like! 20
- 21. Providers in Virtual Kubelet
- 22. IoT Edge with Virtual Kubelet
- 23. Virtual Node architecture in AKS Kubernetes control pane Application architect Infrastructure architect Azure Container Instances (ACI) Virtualnode Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod VM VM VM VM Deployment/ tasks Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod WasteWaste WasteWaste
- 24. Tolerance to Pod Spec
- 25. Affinities to Burst Out to ACI
- 26. Demo – AKS and ACI
- 28. Another demo.
- 29. Extend Kubernetes to Nomad Kubernetes control pane Application architect Infrastructure architect HashiCorp Nomad API VirtualnodePod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod Pod VM VM VM VM Deployment/ tasks WasteWaste WasteWaste Nomad Servers Nomad Client Nomad Client Nomad Client Nomad Client Nomad Client Nomad Job Task Task Task Group
- 30. Demo – Nomad
- 31. Thanks! Questions? Deep Dive: Virtual Kubelet by Jeremy Rickard, Microsoft & Lei Zhang, Alibaba Cloud Wednesday, May 22 • 14:00 - 14:35 Hall 8.0 E1