Introducing the Latest Kubernetes Features for Troubleshooting
summary
Three concrete changes are delivered: structured JSON logs (CAP 1602) defines a standard message + key=value format, adds kobj helpers and new logging calls so component logs become queryable with jq and logging backends, already in component-base alpha and migrating components. contextual logger via logr.WithValues/WithName removes global logger dependency, propagates logger in context, supports per-component V levels and unit test loggers, alpha available. OpenTelemetry/OTLP tracing (CAP 647) instruments kube-apiserver for incoming and outgoing HTTP/gRPC spans, exports OTLP for visualization (Jaeger) with sampling, currently alpha.
AI-written summary · about
chapters (22)
- 0:00Intro
- 0:30Summary
- 2:35Overview of "Structured Logging"
- 3:59Advantage
- 5:00Methods introduced in klog
- 5:42Log message structure
- 7:09Reference to a k8s object
- 8:43Flags introduced in Structured Logging FUJITSU
- 9:55Development plan of Structured Logging FUJITSU
- 10:54Overview of "Contextual Logging"
- 13:41Overview of "logr"
- 15:02Main methods of logr
- 16:21Contextual Logging Use Case 2
- 19:33Usage
- 21:00WithValues/WithName output
- 23:42Development plan of "Contextual Logging"
- 25:03Deprecate klog specific flags in Kubernetes Components FUJITSU
- 26:35What is changed?
- 28:08Overview of "API Server Tracing"
- 32:34Features
- 34:31Example for Tracing
- 36:19Kubelet tracing
related talks
18mRevolutionizing Kubernetes Logging: Structured Logs for Enhanced Monitoring
16mPeeking Under the Hood: Observability of Kubernetes gRPC Internals
41mIntroducing logs in OpenTelemetry: Features and opportunities
11mKubernetes Observability
34mKubernetes Observability with OpenTelemetry
32mUnderstanding Observability in Kubernetes
45mFrom k9s to OpenTelemetry: A guide to observability for your apps in K8s
30mOpenTelemetry: The Road Ahead + Meet the Co...