While disabling the heath endpoint from the application.yml actually removes the endpoint, it is not used by the Fabric8 Maven to remove the readiness and liveness probes definitions from the deployment.

The Fabric8 Maven plugin automatically adds these definitions when the spring-boot-starter-actuator dependency is added to the project classpath. While is it possible to configure these in the plugin configuration, e.g.:

<plugin>
    <groupId>io.fabric8</groupId>
    <artifactId>fabric8-maven-plugin</artifactId>
    <configuration>
        <enricher>
            <config>
              <spring-boot-health-check>
                  <port>4444</port>
              </spring-boot-health-check>
            </config>
        </enricher>
    </configuration>
</plugin>

Currently it is not possible to disable the probes aside from removing the spring-boot-starter-actuator dependency. That seems to be sensible, though one can argue that this can be inconsistent with the application.yml configuration. If you still think this is an issue, I'd suggest you create an issue in the Fabric8 Maven plugin project.

Disabling health checks has no affect #1

Description

Activity

Metadata

Metadata

Assignees

Labels

Projects

Milestone

Relationships

Development

Issue actions