# Kubernetes the Second Week

## Motivation

As someone who learns and teaches Kubernetes on a daily basis, having access to material that is not only good for intro stuff but also works great for teaching intermediate concepts is crucial. This is something I wanted to find for learning. So when I didn't find it, I thought I would make it myself.

## What does second week mean?

In this hypothetical world, I am considering mastering Kubernetes as a 4 week task. In the first week you have done your typical 101 stuff. You know what most of the primitives are (pod, deployment, service). You have deployed your first example application (or maybe your application that you containerized). Kubernetes is still for the most part a mystery. 

What I found that there was a lot of training material for the 101 stuff. There were also a lot for advanced material although those were really focused on very specific problems. What I thought would be great if we had some training material around some lesser known Kubernetes primitive as well as some knobs and buttons in Kubernetes that is crucial for leveling up your K8s game.

## Agenda

1. Level set on week one of K8s.
2. Topics Covered
3. Examples
4. Q/A
5. What for week three?

## $whoami

My name is Mofizur Rahman (Mofi), developer advocate at IBM. Focusing on container and microservices tech stack. I write some go code and collect stickers. 

Find me on almost everywhere @moficodes (twitter, medium, youtube, twitch etc)

All my social links are also on top of every page.


---

# Agent Instructions: Querying This Documentation

If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter:

```
GET https://k8s-second-week.moficodes.dev/second-week/master.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.