Skip to content

Implementation of a service broker which, according to the Open Service Broker API, triggers the deployment of backend services (PostgreSQL, Redis and Co.) via Helm on a Kubernetes cluster.

Notifications You must be signed in to change notification settings

latzinger/ServiceBroker

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 
 
 
 
 
 
 

Repository files navigation

Service Broker

The implementation was part of the lecture Enterprise Programming. The task was to build a service broker which, according to the Open Service Broker API,
triggers the deployment of backend services (PostgreSQL, Redis and Co.) via Helm on a Kubernetes cluster.

Supported Services

  • Redis
  • Postgres

Service Catalog Options

Option Description
Small single small container with low resources
Standard single container with many resources
Cluster clusters of containers

Installation/Usage

Configure Database: application-default.yml

Build Project:

mvn clean install

Authentication Methods

  1. permit all
  2. inMemory Authentication
  3. Database Authentication

###application-default.yml:

osb-security.permit-all = true
osb-security.use-db = false
osb-security.username = epro
osb-security.password = epro

when both permit-all and use-db equals false, inMemory Authentication will be used!

Built With

  • Spring - Spring Framework
  • Maven - Dependency Management
  • Docker - Container Virtualization
  • Kubernetes - Container Orchestration
  • Helm - Package Manager for Kubernetes

Testing

use OSB-Checker application.yml for minimal testing.

  • Postman - API Development Environment

use our Postman-Collection for testing.

Useful Links

Authors

About

Implementation of a service broker which, according to the Open Service Broker API, triggers the deployment of backend services (PostgreSQL, Redis and Co.) via Helm on a Kubernetes cluster.

Topics

Resources

Stars

Watchers

Forks

Releases

No releases published

Packages

No packages published

Languages