K8s and Active Directory Can Be Friends! How to Use Dex to Bridge the Gap
summary
Shows a concrete path to keep Active Directory auth when moving apps to Kubernetes by deploying OpenLDAP as an AD stand‑in, installing Dex as an OIDC bridge, and fronting a legacy app with OAuth2 Proxy. Steps use kind, Helm and kubectl to create users/groups, register OAuth clients, patch the Pac‑Man service to route through the proxy, and port‑forward local hosts entries. Builds an end‑to‑end flow that authenticates and authorizes users (initial 403s fixed by clearing sessions), and demonstrates a working, reproducible configuration.
AI-written summary · about
chapters (21)
- 0:00Start
- 2:01Agenda
- 5:19What Is that Lightweight Directory Access Protocol
- 7:12Rewrite the Pacman Application
- 11:46Prerequisites
- 12:18Installing the Prerequisites
- 12:58Kubernetes in Docker
- 21:15Service Definition
- 22:51Create a Group
- 24:59Interact with this Ldap Server
- 25:17The Ldap Add Command
- 30:23User Search and Group Search
- 33:21Storage Types
- 34:01Static Client Config Configuration
- 34:55Deploying Decks
- 40:43Oauth through Proxy
- 42:41Oauth 2 Client Id
- 43:22Upstream Config
- 54:25The Oauth 2 Proxy Config
- 59:22Log Messages
- 1:03:23Links for Further Reading
related talks
41mKubernetes Auth and Access Control
31mSelecting the Right Identity Provider for Kubernetes: A Comparative Survey
45mBeyond cluster-admin: Getting Started with Kubernetes Users and Permissions
25mExchanging third-party tokens in Dex and how it helps you to build a secure cloud native environment
31mKubernetes OIDC That Works in Practice: Keycloak + RBAC + Kubelogin Without Day‑2 Pain
41mArchitecting Kubernetes-Based Internal Developer Platforms: Essential Patterns...
33mBeyond Cluster-Admin: Getting Started with Kubernetes Users and Permissions
43mSharing is NOT Caring: Stop Sharing Your Kubernetes Cluster Credentials