This document discusses best practices for deploying Kubernetes in production environments. It begins with an introduction to Kubernetes and how it provides benefits like self-healing, load balancing, and horizontal scaling. It then covers the basic architecture of Kubernetes including objects like deployments, pods, nodes, and clusters. The document also discusses maintaining separate development, staging, and production environments. Finally, it provides a checklist of items to consider for production deployments, including health checks, resource monitoring, role-based access control, logging, and autoscaling.

1. K8S in prod
Serena Sensini @ SMART Cloud by OVH

2. ABSTRACT
Technologies belonging to the OCI world are increasingly frequent:
containers on the right, pods on the left ...
Installing and testing Docker or Podman locally is simple, but what happens
when we have to go to production and are dealing with Kubernetes?
So let's define a checklist of checks to be completed when our production
environment is about to go live!

3. Enterprise Architect @ Dedalus spa
Founder of TheRedCode.it
Author of 4 tech books (until now...)

4. TOPIC
INTRO TO KUBERNETES
TOPIC
ARCHITECTURE
TOPIC
STAGING
TOPIC
BEST PRACTICES
TABLE OF CONTENTS

5. #01
TOPIC

6. "KUBERNETES"
It comes from Greek and it means helmsman or
pilot

7. DOCKER VS. KUBERNETES
AT HOME
Wrapping microservices is easy
IN ENTERPRISE
Automatic scaling
Easy portability HA and rollback strategies
Docker is enough Auto-healing capabilitites

8. BENEFITS
SELF-HEALING
Jupiter is a gas giant and the
biggest planet in our System
LOAD BALANCING
Saturn is a gas giant and has
several rings
HORIZONTAL SCALING
Neptune is the farthest planet
from the Sun
CONFIGURATION
MANAGEMENT
Earth is the third planet from the
Sun and the only one with life
AUTOMATIC
ROLLOUTS/ROLLBACKS
Despite being red, Mars is
actually a very cold place
PaaS INTEGRATION
Venus has a beautiful name and
is the second planet from Sun

9. #02
TOPIC

10. HOW IT’S MADE
- To understand how Kubernetes is able to provide these features, it is
useful to have an idea of how it is designed and organized at a high
level
- It can be visualized as an integrated system in levels, in which each
higher level subtracts the complexity found in the lower levels.

12. MAIN OBJECTS
Deployment
Docker Container
Node Process
Node Cluster
Pod
Replica

13. MAIN OBJECTS (v2)
Deployment
kubelet
Worker Node
Pod
Replica
kube-proxy Running Container

14. Pod
Container
Container
Container

15. Container
Container
Container
Deployment
Container
Container
Container

16. Cluster Node

17. #03
TOPIC

18. PROJECT DEVELOPMENT ENV
Development Staging Production

19. Development environment
- Beginning of the project
- Developers may continuously develop or test
their new features without worry on any end
users using it
- This environment constantly changes as the
developers added new features
- It is certainly not stable
- Not a good choice for end users to use it.

20. Staging environment
- Used to test out newer versions of software
before it is moved live
- To maximize your chances of finding any
bugs before release new features to
production
- Need for an environment where we
could have some people to test out new
features before we release it to
production
- Soft launch of the new features

21. Production environment
- If all of the new features were
approved, they are pushed to
production and make it live for
everyone to use and see
- Some ops teams use even a pre-
prod environment

22. HOW TO
On-premises
On cloud
Hybrid

23. IaaS
PaaS
SaaS
ON CLOUD

24. #04
TOPIC

25. CHECKLIST
Healthcheck
Resource Monitoring
RBAC
Logging
Use labels
Autoscaling

26. Steve Maraboli
“Rename your “To-Do” list to your
“Opportunities” list. Each day is a
treasure chest filled with limitless
opportunities; take joy in checking many
off your list.”

27. THANKS!
Do you have any questions?
info@theredcode.it
https://theredcode.it