Continously built container images for spring-boot-admin.
As spring-boot-admin is only available as library without packaged releases, this repository aims to fix that. This repository automatically builds a new image every day and publishes it to the GitHub container registry. Published images can be found here.
Images are tagged with the respective spring-boot-admin version.
- Kubernetes service discovery is included and enabled by default
To configure settings for your instance, either use environment variables as
defined in the spring
documentation
or mount a file called application.yaml to /deployments/application.yaml
when running the container.
Monitored applications are located through Spring Cloud discovery. Two options are available.
The Kubernetes discovery client is on the classpath. When the application runs inside a cluster it discovers other pods/services automatically; no additional configuration is required beyond the usual RBAC allowing the pod to list services and endpoints.
To register targets explicitly — for local testing or for instances outside the
cluster — use the simple discovery client. Each entry needs the target's base
uri and the management.context-path metadata so SBA knows where the actuator
endpoints live:
spring:
cloud:
discovery:
client:
simple:
instances:
my-application:
- uri: http://localhost:18080
metadata:
management.context-path: /actuatorThe key under instances is the application name, and its value is a list,
so you can register several instances of the same application and add further
applications as additional keys:
spring:
cloud:
discovery:
client:
simple:
instances:
my-application:
- uri: http://my-application-1:18080
metadata:
management.context-path: /actuator
- uri: http://my-application-2:18080
metadata:
management.context-path: /actuator
another-application:
- uri: http://another-application:8080
metadata:
management.context-path: /actuator