Service catalog and the problem of managing dependencies in Kubernetes
- Developers using Kubernetes often need to manage dependencies like databases and message queues
- Manually provisioning and managing these dependencies is not scalable
- Service catalog was an attempt to solve this problem by providing a single source of truth for all infrastructure and application dependencies
- Service catalog was built on top of the open service broker API, which allows for decoupling between service providers and consumers
- One issue with service catalog was its complexity and lack of adoption