How Container Runtime Matters in Kubernetes?
Container Orchestrator Kubernetes utilizes Container Runtime to provide low-level pod/container management and operations at the node level. The capabilities & performance of these Container runtimes …
| Talk Title | How Container Runtime Matters in Kubernetes? |
| Speakers | Kunal Kushwaha (Senior Engineer, NTT OSSC) |
| Conference | Automotive Linux Summit & Open Source Summit Japan |
| Conf Tag | |
| Location | Tokyo, Japan |
| Date | Jun 19-22, 2018 |
| URL | Talk Page |
| Slides | Talk Slides |
| Video | |
Container Orchestrator Kubernetes utilizes Container Runtime to provide low-level pod/container management and operations at the node level. The capabilities & performance of these Container runtimes affects the overall system and thus affect workload running in a cluster. Kunal will present evaluation and comparative study of major Container Runtime options (cri-containerd, cri-o, frakti) available for K8s and how each one behaves in terms of various types of workloads along with features/capabilities that compliment them. This shall be helpful while designing/building Kubernetes Stack for your workloads. Few of workload patterns shall be covered as -Serverless framework -Peak hours demand for services (quick scale-up) -Mean Time To Recovery (MTTR) (DevOps) -Long Running containers (databases/monolithic/legacy apps) -Application with high security (Meeting approved security standards)
