This is an implementation of a Service Broker that uses Helm to provision instances of Redis. This is a proof-of-concept for the Kubernetes Service Catalog, and should not be used in production. Thanks to the mariadb broker repo.
- Kubernetes cluster
- Helm 2.x
- Service Catalog API - follow the walkthrough
The Redis Service Broker can be installed using the Helm chart in this repository.
$ git clone https://github.com/yqf3139/redis-broker.git
$ cd redis-broker
$ helm install --name redis-broker --namespace redis-broker charts/redis-broker
To register the Broker with the Service Catalog, create the Broker object:
$ kubectl --context service-catalog create -f examples/redis-broker.yaml
If the Broker was successfully registered, the redis ServiceClass will now
be available in the catalog:
$ kubectl --context service-catalog get serviceclasses
NAME KIND
redis ServiceClass.v1alpha1.servicecatalog.k8s.io
$ kubectl --context service-catalog create -f examples/redis-instance.yaml
This will result in the installation of a new Redis chart:
$ helm list
NAME REVISION UPDATED STATUS CHART NAMESPACE
i-3e0e9973-a072-49ba-8308-19568e7f4669 1 Sat May 13 17:28:35 2017 DEPLOYED redis-0.6.1 3e0e9973-a072-49ba-8308-19568e7f4669
$ kubectl --context service-catalog create -f examples/redis-binding.yaml
A secret called redis-instance-credentials will be created containing the
connection details for this Redis instance.
$ kubectl get secret redis-instance-credentials -o yaml
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent