Improving Security and Observability of YugabyteDB on Kubernetes
summary
YugabyteDB runs on Kubernetes with a required minimum of three masters and three tablet servers and delivers single‑digit‑millisecond latency while supporting the Postgres protocol. The deployment uses Istio + Envoy sidecars to enforce mutual TLS namespace‑wide, automate certificate rotation, and apply destination rules for masters/tablets. Observability combines Kiali, Jaeger, Prometheus and Grafana with Yugabyte metrics merged into one dashboard, and an experimental Envoy Postgres filter extracts DB metrics without touching the database.
AI-written summary · about
chapters (14)
- 0:00Introduction
- 1:23About YugabyteDB
- 3:35Deployment on Kubernetes
- 5:26What is Service Mesh
- 7:54Histo
- 10:05Security Best Practices
- 12:44Implementing Mutual TLS
- 13:59Creating Destination Rules
- 14:48Observability
- 16:16User Interface
- 17:05Detailed View
- 18:09Histo Workflow
- 19:10Histo Filters
- 21:37Example
related talks
01h 29mYugabyteDB DBA Fundamentals
18mBulletproofing your YugabyteDB Infrastructure to Reduce Risk
25mProtecting Your Data in Yugabyte Cloud with HashiCorp
19mTop Security Questions: Delight Your CISO and Protect Your Business
24mScaling to Billions of Internet Observations per Day
18mBuilding a Scalable, Resilient System for Real-Time Fraud Detection
49mUnified Observability: Monitoring Postgres Anywhere with OpenTelemetry
11mKubernetes Observability