|
|
| (100 intermediate revisions by the same user not shown) |
| Line 1: |
Line 1: |
| =Introduction=
| |
| =Containers=
| |
| This all started with VMWare where the total resource could be divided up to run more than one application on difference virtual machines. But VMWare required an OS on every machine and licenses in the case of Windows. They also needed managing, e.g. patching, Anti-virus and patching. Along came containers which shared the OS.
| |
| <br>
| |
| [[File:Containers Overview.png|500px]]
| |
| <br>
| |
|
| |
|
| =Docker=
| |
| Docker Inc. Docker is a company which gave the word technology for containers. They are now a company which provides services around the company.
| |
| <br>
| |
| <br>
| |
| Docker is Open source and known as Community Edition (CE). The company Docker releases an Enterprise Edition (EE).
| |
| <br>
| |
| The general approach is to
| |
| *Create an image (docker build)
| |
| *Store it in a registry (docker image push)
| |
| *Start a container from it (docker container run)
| |
| The differences between EE and CE are shown below
| |
| [[File:Docker Diffs.png|500px]]
| |
|
| |
| =Kubernetes=
| |
| Kubernetes came out of Google and Open Source. Greek for helmsman or k8s (Kates). Kubernetes is an orchestrator and can schedule, scale and update containers. There are alternatives like Docker Swarm
| |
| <br>
| |
| [[File:Kubernetes.png|500px]]
| |
| ==Architecture==
| |
| ===Overview===
| |
| Apps are put in a container, wrapped in a pod and deployment details. They are provisioned on a Node inside a K8s Clustoer<br>
| |
| [[File:K8 Arch.png|600px]]
| |
| ===Master===
| |
| In general these are a hosted services on the cloud but you can run them locally on a linux box.
| |
| *This is the front-end to the control plane
| |
| *It exposes a RESTFul API consuming JSON and Yaml
| |
| *We send manifests describing our apps to this
| |
| <br>
| |
| The Cluster Store for users with large changes often separate this
| |
| <br>
| |
| <br>
| |
| The controllers controls
| |
| *Node Controller
| |
| *Deployment controller
| |
| *Endpoints/EndpointSlice
| |
| <br>
| |
| The scheduler
| |
| *Watches for new work
| |
| *Assigns Work to the cluster nodes
| |
| <br>
| |
| [[File:K8 Master3.png|400px]]
| |
| ===Kubernetes Nodes===
| |
| Now its time for the Nodes<br>
| |
| [[File:K8 Nodes.png|500px]]
| |
| ====Kubelet====
| |
| The Kubelet is the Main Kubernetes agent it
| |
| *Registers node with the cluster
| |
| *Watches API Server for work tasks (Pods)
| |
| *Executes Pods
| |
| *Reports to the master
| |
|
| |
| ====Container Runtime====
| |
| *Can be Docker
| |
| *Pluggable via Container Runtime Interface (CRI)
| |
| *Generally is Docker or containerd, other like gVisor and katacontainers exist
| |
| *Does the stop and starting of containers
| |
| ====Kube Proxy====
| |
| *The Networking Component
| |
| *Does light-weight load balancing
| |
| ===Declarative Model/Desired State===
| |
| We describe what we want the cluster to look like but we do not care how it happens. Kubernetes constantly checks the desired state matches the observed state.
| |
| ===Pods===
| |
| A pod is a shared execution environment and can container one or more containers. It is the Pod which has a unique IP. Containers within the same pod must allocate unique ports if they are to talk to each other or the outside world. The same for volumes etc.When scaling you scale Pods not Containers.<br>
| |
| [[File:K8 Pods.png|400px]]
| |
| <br>
| |
| Multi container Pods are for two different but complimentary containers which need to be aligned. An example of this might be a service mesh. For example the mesh container could be responsible for encryption or decryption. '''Note''' Deployment of Pods is atomic
| |
| <br>
| |
| [[File:K8 Mesh2.png]]
| |