--- title: Introduction collection: docker-k8s-fundamentals author: Akash Kadlag updated: 2026-11-18 source: https://docs.chaicode.com/docker-k8s-fundamentals/introduction --- # Introduction ## Fundamentals of **Docker** & **Kubernetes** From "it works on my machine" to software you can ship anywhere. Fundamentals of **Docker** & **Kubernetes** Welcome everyone. Tonight is the fundamentals of Docker and Kubernetes. The journey we take: from the classic frustration of 'it works on my machine' to software you can ship anywhere and it just runs. This chapter is the introduction: who I am, what we cover, what we skip, and what you need to follow along. ## **Thank You** so much. Where this talk begins. **Thank You** so much. The source slide for this chapter was an empty placeholder titled New slide with no items, so this opening keeps only what it had: its place as the first slide of the Introduction. Use this slide to welcome the audience and say in one sentence what the talk is about. No facts, numbers or examples were given in the source, so none are added here; fill in your opening points from your own material. Hand over to the next slide once the subject of the talk has been stated. ## "Be **good at the basics** first..!" Every good engineer I know says "Be **good at the basics** first..!" Ask the chat: type 1 if you've ever said this, or heard it. Pause and let the ones roll in. Everyone has lived this. Say: by the end of tonight, you'll know exactly why this happens and which tools killed this sentence. ## Akash Kadlag Who am I Akash Kadlag Your Next Tech Partner Sr. Software Developer Educator @ ChaiCode Find me: YT, X, LinkedIn, GitHub, Insta at @yntpdotme Website: yntp.me Keep this to about 60 seconds. Full stack developer and freelancer, working across full-stack and DevOps. Previously at iNeuron (verify or edit this line). Community lead (add the community name). Tell one personal line: the first time Docker saved you, or the first deploy you broke. Everything is at @yntpdotme, or yntp.me. ## What we're **not** covering today What we're **not** covering today Deep Kubernetes: networking, storage, Helm, operators, security Production cluster setup or cloud-specific services Every Docker command or flag Say: Kubernetes is a whole ocean. Today we just learn to swim at the shore. We skip the deep Kubernetes topics: networking, storage, Helm, operators, security. No production cluster setup, no cloud-specific services, and not every Docker command or flag. The deep dives come in upcoming webinars and on YouTube. ## What we're covering today What we're covering today Why: Why Docker and Kubernetes exist: the problems they solve Foundations: A short history, the SDLC, what DevOps is, why CI/CD matters Docker: Containers, how they differ from **VMs**, running many with Compose Kubernetes: What it is and why we need it, the basics only Adopting it: How to learn DevOps, Docker and Kubernetes Five parts tonight. First, why these tools exist and what problems they solve. Then foundations: a short history, the software development life cycle, what DevOps is, and why CI/CD matters. Docker: containers, how they differ from virtual machines, and running multiple containers with Compose. Kubernetes: what it is and why we need it, basics only. And finally how to learn and adopt all of this, including certifications. ## What helps you follow along What helps you follow along Terminal: Basic usage: cd, ls, running commands An app: You've built or run some app in Node, Python or Java, any is fine Basics: A rough idea of a **server**, a **port** and an environment variable Config formats: JSON and YAML, because Docker and Kubernetes are configured with them You don't need much. Basic terminal usage: cd, ls, running commands. You should have built or run some app before, in Node, Python or Java, whichever. A basic idea of what a server, a port and an environment variable are. And config file formats, JSON and YAML, because that's how Docker and Kubernetes are configured. Next slide covers them. ## Configuration formats Configuration formats YAML is a superset of JSON, so Kubernetes accepts both. Same data on both sides: a service named web, 3 replicas, ports 3000 and 8080, and an environment variable NODE_ENV set to production. YAML is a superset of JSON, so Kubernetes accepts both. People prefer YAML because it's shorter and allows comments. Say: we'll see YAML twice tonight, in Docker Compose and in Kubernetes. Now you can read both. ## How to read and write **YAML** How to read and write **YAML** Indentation is structure: Use spaces, never tabs key: value: Put a space after the colon - starts a list item: Each item on its own dash # starts a comment: JSON can't have comments Quote values that look like something else: Write version: "1.20", or it becomes the number 1.2 true and false need no quotes: Write enabled: true, not "true" Five rules and you can read any YAML file tonight. Indentation is structure, and it must be spaces, never tabs. Key, colon, space, value. A dash starts a list item. A hash starts a comment, which JSON cannot do. Quote values that look like something else: version: "1.20" with quotes, because unquoted it becomes the number 1.2. ![A meme image of a bored tabby cat resting its head down on a surface.](https://docs.chaicode.com/cdn-cgi/image/width=1600,format=auto,fit=scale-down/assets/8220a627bf9e55ee09e9acdf9f045600b3d11f5152eb6319db5446c431ba6c2a.png) THESE PRESENTATIONS ARE AWESOME JUST KIDDING, I'M BORED ## Where to read, play and keep learning Where to read, play and keep learning Read: docs.chaicode.com Play in the browser: labs.chaicode.com Learn DevOps: ChaiCode DevOps Playlist on **YouTube** Three places to go after tonight. Read the docs at docs.chaicode.com. Play in the browser at labs.chaicode.com, no install needed. To learn DevOps properly, follow the ChaiCode DevOps playlist on YouTube. ## प्रेजेंटेशन में जो भी कहूंगा सच कहूंगा, **सच के सिवा कुछ नहीं कहूंगा...** प्रेजेंटेशन में जो भी कहूंगा सच कहूंगा, **सच के सिवा कुछ नहीं कहूंगा...** Quick recap of the chapter: you know who I am, what we cover, what we skip, and what you need. You can now read both JSON and YAML, which you'll see in Docker Compose and Kubernetes. Next chapter: why these tools exist and the problems they solve.