The groups of containers. The smallest schedulable unit. Can just be one container. You may end up with 2 containers that are tightly coupled and you put them in the same pod.

Machines. They are either baremetal or VMs in google cloud. A node is just a machine.

This is the real power of Kube. A deployment is a statement of the desired number of pods you want. You schedule onto the nodes.

It's a declarative start. You declare what you want and Kube will schedule that for you and monitor it.

What happens if a node becomes unhealthy and needs to be removed?

Kube will recognize this and quickly bring up new containers on healthy nodes, after which it will observe this happened. The best part is, this can happen while you're sleeping. You just declare what you want and Kube will handle the rest to make sure you are where you want to be.

This is a group of identical pods that host an front end or backend. What you would typically call a service. The individual pods can be located anywhere in your cluster but the service keeps the relevant pods tied together to fulfill the service.

Google Kubernetes Engine

This is different than kube in general. It's just how Google deals with Kube. Kube is an open source project and google is trying to build the best platform to run Kube on. GKE has 3 benefits: cluster autoscaling (add nodes to handle demand, scale back to save money, node auto repair (detect unhealthy nodes and recreate them, node auto upgrade (stay up to date with the latest features and security patches without lifting a finger).

Gitlab integration with GKE

You just need to merge your code and GKE does all the rest. Gitlab CI/CD jumps in to take the merged code and deploy it.

Help

Options

focusNode

Didn't know it?
click below

Knew it?
click below

Don't Know

Remaining cards (0)

Know

retry

shuffle

restart

0:00

Embed Code - If you would like this activity on your web page, copy the script below and paste it into your web page.

Normal Size Small Size show me how

Kubernetes

Question	Answer
Pods	The groups of containers. The smallest schedulable unit. Can just be one container. You may end up with 2 containers that are tightly coupled and you put them in the same pod.
Containers	A unit of measure for apps.
Nodes	Machines. They are either baremetal or VMs in google cloud. A node is just a machine.
Deployment	This is the real power of Kube. A deployment is a statement of the desired number of pods you want. You schedule onto the nodes.
How Kubes works	It's a declarative start. You declare what you want and Kube will schedule that for you and monitor it.
What happens if a node becomes unhealthy and needs to be removed?	Kube will recognize this and quickly bring up new containers on healthy nodes, after which it will observe this happened. The best part is, this can happen while you're sleeping. You just declare what you want and Kube will handle the rest to make sure you are where you want to be.
Service	This is a group of identical pods that host an front end or backend. What you would typically call a service. The individual pods can be located anywhere in your cluster but the service keeps the relevant pods tied together to fulfill the service.
Google Kubernetes Engine	This is different than kube in general. It's just how Google deals with Kube. Kube is an open source project and google is trying to build the best platform to run Kube on. GKE has 3 benefits: cluster autoscaling (add nodes to handle demand, scale back to save money, node auto repair (detect unhealthy nodes and recreate them, node auto upgrade (stay up to date with the latest features and security patches without lifting a finger).
Gitlab integration with GKE	You just need to merge your code and GKE does all the rest. Gitlab CI/CD jumps in to take the merged code and deploy it.

Created by: johnscraigslistalerts

"Know" box contains:
Time elapsed:
Retries: