MSmszostok·Dec 4, 2019
Hi, I will try to highlight some benefits.
You probably know the Helm, right? Helm is a great way to install and manage the life cycle of complex Kubernetes applications.
The Service Catalog mentioned by @derberg gives you an option to define some plans and automates injecting credentials into your business application.
And Helm Broker combines those two mature CNCF projects.
Benefits?
With the pure Helm Chart end-user needs to go manually through the whole Helm value.yaml and figuring out what should be adjusted to have a free trier. With Helm Broker, you have an option to create predefined plans like free trier, enterprise etc. which can be then selected by the user.
Second thing is that when you are installing e.g. MySQL via Helm Chart then final configuration like pass,URL, etc. will be printed as a plain text and users need to inject
Read the rest
them manually into a business application. With Helm Broker this process is automated and a user can simply create a binding between MySQL instance and business application and as a result, all necessary credentials will be injected into this application.
Additionally, you gain an extra security layer which prevents your e.g. MySQL instance from being removed when it is still in use by external applications. Such prevention is not possible when you are using only Helm.
If you want to play with that, check the installation docs: https://github.com/kyma-project/helm-broker/blob/master/docs...
and example use-case: https://github.com/kyma-project/helm-broker/blob/master/docs...
I can spoiler that in the near future we will create the interactive tutorial, similar to that one: https://katacoda.com/rafter/scenarios/rafter, so getting familiar with Helm Broker will be much easier.