Making Sense Of Configuration and Service Discovery On Kubernetes
summary
Compares concrete options for external config and discovery on Kubernetes: using config maps and secrets mounted as a volume with spring.config.import:configtree versus keeping Spring Cloud Config Server (extended with a Kubernetes environment repo) and using a Spring Cloud Kubernetes discovery server so existing discovery clients and Spring Cloud LoadBalancer keep working. Demo builds three apps (config server, discovery server, frontend/sensor), runs RabbitMQ, deploys five sensor pods, shows config mounted files, and describes a config watcher that calls the refresh endpoint to update without full cluster restarts.
AI-written summary · about
chapters (14)
- 0:00Start
- 4:40Spring Cloud and Kubernetes
- 10:45Spring Config Import
- 11:25Config Tree
- 13:49Service Discovery
- 20:35The Spring Cloud Kubernetes Discovery Server
- 21:59The Config Watcher
- 23:39Demo
- 26:13Spring Data Source
- 36:28Deploy the Discovery Server
- 38:34Configuration Server
- 39:53Discovery Server
- 41:52Do I Need To Use Spring Cloud
- 44:10Config Maps and Secrets
related talks
49mSpring Cloud on Kubernetes
46mExperiences from using discovery services in a microservice landscape
31mDeploying Spring Boot apps on Kubernetes
44mSpringing into Kubernetes
44mConfiguration Management with Kubernetes, a Spring Boot use case
48mKontain Your Spring
27mDeploying Spring Boot Apps on Kubernetes
42mKubeBoot - Spring Boot deployment on Kubernetes
