Logging Operator: Multi-Tenant Kubernetes Logging
Kubernetes gives every pod a place to write logs, but it leaves the actual logging pipeline up to you. Once you try to ship those logs anywhere, you face choices about collectors, routing, buffering, isolation, and how to keep one noisy team from affecting everyone else.
In this episode, Whitney Lee stands at the lightboard with Peter Wilcsinszky to look at why this happens and how the Logging Operator helps. They walk through the realities of node-level collection, what makes routing tricky, and how Flows and Outputs give teams a clear, Kubernetes-native way to control where their logs go.
Learn how to automate deployment and configuration of a K8s logging pipeline, and give your developers the control they need without giving up governance.
If you want a simple picture of why logging feels complicated on Kubernetes and what the Logging Operator does to untangle it, this 🌩️Thunder episode brings it into focus.
Prefer the full ⚡ Enlightning episode?
Evolving Multi-tenant Kubernetes Log Collection with the Logging Operator → https://www.youtube.com/live/CPh6GIhJ1JU
Watch all ⚡ Enlightning episodes → • ⚡️ Enlightning
Watch all 🌩️ Thunder episodes → • 🌩️ Thunder
٩( ᐛ )و Subscribe to Whitney’s YouTube channel → / @wiggitywhitney
#Kubernetes #LoggingOperator #KubernetesLogging #FluentBit #Fluentd #CNCF #DevOps #observability
*CHAPTERS:*
0:00 - The Problem with Kubernetes Logs
0:51 - Before Logging Operator
1:22 - What is Logging Operator?
1:58 - How Log Collection Works (And Where It Breaks)
5:46 - Logging Operator to the Rescue!
5:56 - The Secret Sauce: Flows & Outputs
7:41 - What Logging Operator Solves
10:46 - The Telemetry Controller
14:17 - How to Get Involved
▬▬▬▬▬▬ ⚡️ Related Links ⚡️ ▬▬▬▬▬▬
🔗 Logging Operator docs → https://kube-logging.dev/
🔗 Telemetry Controller → https://github.com/kube-logging/telem...
🔗 CNCF Slack → https://slack.cncf.io/