![]() Community, discussion, contribution, and support In the Kubernetes ecosystem, the CNCF Sandbox Cloud Native Buildpacks project has proposed a buildpack-specific specification exclusively addressing the application developer portion of this pattern. ![]() Other open source projects like the Open Service Broker aim to help with this pattern on those non-Kubernetes platforms. ![]() Heroku pioneered this model with Add-ons, and Cloud Foundry adopted similar ideas with their Services. The pattern of Service Binding has prior art in non-Kubernetes platforms. Platforms expect to retrieve secrets from Service Providers and expose them to Application Developers consistently and predictably.Service Providers expect their secrets to be collected and exposed to consumers consistently and predictably.Application Developers expect their secrets to be presented consistently and predictably within a container.The benefit of Kubernetes-wide specification is that all of the actors in an ecosystem can work towards a clearly defined abstraction at the edge of their expertise and depend on other parties to complete the chain. It aims to create a widely applicable mechanism without excluding other strategies for systems that it does not fit easily. This specification aims to create a Kubernetes-wide specification for communicating service secrets to workloads in a consistent way. To combat this, we see teams adopting internal patterns for how to achieve this workload-to-service linkage. While there is a good deal of value to this flexibility, large development teams lose overall velocity dealing with each unique solution. Each service provider suggests a different way to access their secrets, and application developers consume these secrets in a way specific to each workload. Today in Kubernetes, the exposure of secrets for connecting application workloads to external services such as REST APIs, databases, event buses, and many more is manual and bespoke. ![]() Service Binding Specification for Kubernetes
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |