Paketo Bindings for Spring Boot Applications

1 minute read

Service Binding Specification for Kubernetes standardizes exposing backing service secrets to applications. The application should be prepared to use the bindings projected into the container. This article explains how to use Cloud Native Buildpacks and Spring Cloud Bindings Java library to prepare a Spring Boot application to consume the bindings.

Cloud Native Buildpacks transform your application source code into OCI images that can run on any cloud. The Paketo Spring Boot Buildpack is a Cloud Native Buildpack that helps to contribute Spring Cloud Bindings as an application dependency.

The Spring Cloud Bindings library enable automatic Spring Boot configuration based on the system property. The Paketo buildpacks sets this property value to true if the bindings exists in the /platform/bindings directory at build-time. The name of the sub-directory is considered as the name of the binding. Within each directory, there should be a file named type with the name of the type of binding. You can see the list of supported types in the Spring Cloud Bindings README.

For example, if you want to build the PetClinic REST server sample application with PostgreSQL backend, create a directory with a file named type like this:

mkdir /tmp/postgres
echo "postgresql" > /tmp/postgres/type

Now you can build the application image like this:

git clone
cd spring-petclinic-rest
pack build --path . --builder paketobuildpacks/builder:base\
--volume /tmp/postgres:/platform/bindings/postgres spring-petclinic-rest

The Paketo Buildpacks will look for bindings in $SERVICE_BINDING_ROOT at runtime. If an implementation of Service Binding Specification for Kubernetes project the bindings, your Spring Boot Application should connect to PostgreSQL database.

When running the abive application, set the active spring profile through an environment variable like this: SPRING_PROFILES_ACTIVE=postgres,spring-data-jpa

If you want to test the above application, create these files with valid values:

├── database
├── host
├── password
├── port
├── type
└── username

For testing the connectivity, you can run the container using docker:

docker run --env SERVICE_BINDING_ROOT=/bindings --env SPRING_PROFILES_ACTIVE=postgres,spring-data-jpa\
--volume /tmp/postgres:/bindings/postgres --rm -p 9966:9966 spring-petclinic-rest:latest