Kubernetes

Description:

• Container orchestration engine by:
  • Declaratively state the config
  • imperatively (experienced)
• Automating deployment, scaling, and management of containerized applications.
  • good for Microservices
• The system is divided into a set of primary components that run as the Control Plane and a set of nodes that run containers.
• Docs and Ref
• Frontend refers to backend K8s service so if the backend ip change, the service will update it
• Orchestrating the Cloud with Kubernetes | Google Cloud Skills Boost
• Autoscaling: https://www.cloudskillsboost.google/course_sessions/7226348/labs/451701

A. Documentations

B. Getting started

C. Concepts:

1. Overview:

• Objects in K8s
  • Persistent entities in the Kubernetes system.
    • Kubernetes uses these entities to represent the state of your cluster.
  • Idenfied:
    • unique name, can only have 1 object of same name at any moment
    • unique identifier, generated by k8s
  • Has:
    • Object spec: desired state
    • Object status
  • Kubernetes Namespaces
• Components:
  • 
  • Control Plane
  • K8s Node

  • Add-ons:

2. Cluster Architecture:

3. Containers:

4. Workloads:

• K8s pod
• Workload management:
  • K8s Deployment
  • K8s ReplicaSet
  • K8s StatefulSets
  • s
  • K8s CronJob

5. Service, load balancing and networking:

• K8s service:
  • Expose an application running in your cluster behind a single outward-facing endpoint, even when the workload is split across multiple backends.
• …
• …

6. Storage:

• K8s Volumes

D. Tasks:

1.

6.

8. Run applications:

• …
• K8s Horizontal Pod Autoscaling vs K8s Vertical Pod Autoscaler
• ..
• K8s Pod Disruption Budget
• s

9. Run jobs

---

Service:

• An abstraction which defines a logical set of Pods and a policy by which to access them.

kubectl