docker-k8s-fundamentals
Introduction
On this page
- Fundamentals of **Docker** & **Kubernetes**
- **Thank You** so much.
- "Be **good at the basics** first..!"
- Akash Kadlag
- What we're **not** covering today
- What we're covering today
- What helps you follow along
- Configuration formats
- How to read and write **YAML**
- Where to read, play and keep learning
- प्रेजेंटेशन में जो भी कहूंगा सच कहूंगा, **सच के सिवा कुछ नहीं कहूंगा...**
Notes
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.
Notes
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.
Notes
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.
Notes
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.
Notes
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.
Notes
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.
Notes
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.
Notes
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.
Notes
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.
10
Notes
THESE PRESENTATIONS ARE AWESOME
JUST KIDDING, I'M BORED
Notes
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.
Notes
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.