Skip to content

Document that properties that change an application's beans are fixed at build time #35032

@derkoe

Description

@derkoe

When running a native-built Spring Boot application on Kubernetes the liveness and readiness probes are not active (they both return a 404).

How to reproduce:

  1. Go to start.spring.io and select Web, Actuator and GraalVM Native
  2. Build a native image of your application (mvn spring-boot:build-image -Pnative)
  3. Launch the application in Kubernetes (or set the appropriate environment when running locally docker run -it --rm -e KUBERNETES_SERVICE_HOST=localhost -e KUBERNETES_SERVICE_PORT=8080 -p 8080:8080 docker.io/library/demo:0.0.1-SNAPSHOT)
  4. Open http://localhost:8080/actuator/health/liveness

Expected result - HTTP 200 with body {"status":"UP"}, actual result HTTP 404.

Metadata

Metadata

Assignees

Labels

theme: aotAn issue related to Ahead-of-time processingtype: documentationA documentation update

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions