Skip to content
Hallway
0:00 / 0:00

#kubernetes#kubernetesapi#persistentvolumes

Kubernetes Design Principles: Understand the Why - Saad Ali, Google

CNCF [Cloud Native Computing Foundation]

141K subscribers • 77 videos on Hallway • Conference channel

YouTube
  • Recommended by 3 people: 3 in engineering communities.
  • A classic. People kept recommending it from 2020 to 2026.
  • Presented by Saad Ali, Software Engineer at Google
  • May be out of date. Uploaded 7 years ago, in an area where tools change fast.

Intermediate. Assumes working knowledge.

146K views7 years ago3 recommendations

Cloud and DevOpsSoftware designKubernetesSoftware architectureDesign patterns

Saad Ali explains the design principles behind Kubernetes, including its API structure, component interactions, and resource abstractions.

Join us for Kubernetes Forums Seoul, Sydney, Bengaluru and Delhi - learn more at kubecon.io Don't miss KubeCon + CloudNativeCon 2020 events in Amsterdam March 30 - April 2, Shanghai July 28-30 and Boston November 17-20! Learn more at kubecon.io. The conference features presentations from developers and end users of Kubernetes, Prometheus, Envoy, and all of the other CNCF-hosted projects Kubernetes Design Principles: Understand the Why - Saad Ali, Google Kubernetes is quickly becoming indispensable for managing and deploying workloads on distributed systems across both cloud and on-prem environments. While most people are now familiar with how to use Kubernetes, few are aware of the “why” behind it? Why does the Kubernetes API look the way it does? Why do Kubernetes components only interact with each other through the Kubernetes API? Why is there a PersistentVolumeClaim object when you could easily reference a volume directly from a pod? To answer these questions and help you develop a deeper understanding of Kubernetes, this talk exposes the principles underpinning the design of Kubernetes. To learn more: sched.co/IrkE

Why it's here

3 people recommend this

What people say. Recommended for understanding the underlying design philosophy of Kubernetes and how concepts like persistent volumes are abstracted.

u/jagagayayyaaahin r/kubernetes • Recommends

On “Hello my company wants to move it's VMs in gcp to kubernetes”

Good video on the value of Kube and what is does - link to this video "Kubernetes Design Principles: Understand the Why - Saad Ali, Google" 1. Write a Dockerfile for your application and run it locally based on any existing automation of the VM environment 2. Figure out all the external dependencies - databases etc - containerise them too 3. Write it as a Docker Compose setup - syntax is more succinct and simpler to get your head around at first 4. Enable Kubernetes API on Docker Desktop 5. Use Kompose to convert the compose setup to Kubernetes manifests, try and apply them, fix things. (or write from Kube scratch - harder but maybe more valuable in actually learning the abstractions) 6. Try deploying…
5View on Reddit

u/exmachinalibertasin r/kubernetes • Recommends

On “Help: I just can't wrap my head around persistent volumes vs volumes”

I just wanted to come back and tell you I was watching this video and they give a reasonable explanation for persistent volumes versus volumes. Basically, they wanted to abstract away storage from the pod spec, so that deployments could more easily move to different clusters. With what I referred to above as "volume types" (i.e. what you call "volumes"), those are for the most part external third party storage providers that don't change if you move your pod definition from one cluster to another. Whereas if you are using in-cluster persistent volumes, then of course the storage location is changed when you change clusters. So PVs and StorageClasses were designed in order to abstract away…
1View on Reddit

u/DPRegularin r/kubernetes • Recommends

On “Dumb sysadmin here. Anything I should learn before diving into Kubernetes?”

You might find this video interesting: link to this video
1View on Reddit