Kubernetes! Demystifying a few “magic words” and terms

Kubernetes is a container orchestra-tor, that support rocket containers and docker containers.
When using Kubernetes we have some main keywords that are going to be used in his infrastructure:
PODS
PODS are the commons containers that can have the same functions, like by example you can have many PODs with mysql, nginx, redis, etc.
So if needed, you can just schedule a new POD with all those containers specified before (mysql, nginx, redis).
Replication Controller (RC)
This is what is going to manage how many PODs we must have active by node. We can setup by example a node that must have 5 web-servers active, so if one of those PODs dies, the replication controller will do the job to scale a new PODs with that web-server.
He is what will manage the POD’s quantities and scale your clusters if necessary.
Services
This is what is going to control the ip’s, and ports that those PODs are going to use.
With the services we can assure that a new PODs that was escalated to replace a POD that died, will use the same addresses.
Namespace
It’s important that the Namespace correspond to literaly the names of the environments that Kubernets will setup. It’s the Namespace that will be used to replicate, configure the roles and permissions for each environment and others.
etcd
ETCD it’s a storage (that uses key and values patterns) used by kubernetes to save, manage and use keys and values like hosts, ip’s, and many other values that can be useful for Kubernetes.
Services Proxy
This is literally the proxy that will check the hosts and addresses that are sending the requests or commands, and it will redirect them to the correct assigned instances based on Services configs.
Kubernetes Master
This is the manager from Kubernetes, the resource that will verify the health states from the PODs and will manage the PODs creation between the clusters.
Kubelet
This is the main agent that will be run in all the hosts of Kubernetes.
