are faster to boot than virtual machines. ・Applications are isolated in containers, which is convenient. On the other hand, containers become disorganized and difficult to manage.
for managing containerized workloads and services, that facilitates both declarative configuration and automation. (From Kubernetes Document https://kubernetes.io/docs/concepts/overvie w/what-is-kubernetes/)
configuration files called manifests 2. Standardized and abstracted by Kubernetes API, no need to know server-specific settings 3. Reconciliation Loop Kubernetes Makes Container Operations Convenient
name: test image: nginx:1.14.2 resources: requests: memory: "100Mi" Example of manifest:nginx container Which server to deploy? What Operating System to use?Specification of the server memory? No need to worry!
because it automates what kubectl apply does. GitOps:Pull-based model. Because it is declarative, the managed manifest is always the correct configuration.
• “Logging in to a VM, checking it with ps or systemctl, and looking at the log file" is no longer an option. Log! Metrics! Alert! Important! Observability
to Blow Up Your Kubernetes - Jian Cheung & Joseph Kim, Airbnb https://www.youtube.com/watch?v=4CT0cI62YHk Keynote: How Spotify Accidentally Deleted All its Kube Clusters with No User Impact - David Xia https://www.youtube.com/watch?v=ix0Tw8uinWs Kubernetes Failure Stories https://k8s.af