Completed
Solution idea
Class Central Classrooms beta
YouTube videos curated by Class Central.
Classroom Contents
Introducing Log Tracking Feature to Revolutionize Kubernetes Observability
Automatically move to the next video in the Classroom when playback concludes
- 1 Intro
- 2 What is Kubernetes(k8s)?
- 3 Declarative operation Define the elements/conditions in yaml/json The definition describes the final state, not the procedure Can check the change history by version control such as Git All you have …
- 4 What does k8s cluster consist of? The cluster consists of Control Plane and Nodes Control Plane Apiserver Controller manager
- 5 What is Control Plane doing? Make global decisions about the cluster, as well as detecting and responding to cluster events.
- 6 What is Node doing? Run the application deployed in the cluster Maintaining running pods and providing the Kubernetes runtime environment
- 7 Overview of K8s logging
- 8 The problem want to solve Difficult to investigate logs across components
- 9 Solution idea
- 10 Tracking the cause of operation Fujitsu
- 11 Check the impact of system failure
- 12 Overview of realization
- 13 Issues in implementation There are implementation issues in the following situations: Issue 1: Multiple requests are the cause of processing Issue 2: Multiple components operate in a chain with one r…
- 14 Multiple requests are the cause of processing When multiple requests are processed at the same time, it is necessary to associate multiple IDs with the processing.
- 15 The object to be processed is different from the object of the trigger Ex. Pod update processes replicaset with trigger
- 16 Current status Proposing KEP to enhance the logging function. We are thinking of an implementation and system design that can solve all the implementation issues.
