Grpc health checks not exposed anymore

[cdprete]

Hello.

I'm using version 1.0.2 of the library with Spring Boot 4.0.3 in AOT and I realized that the Health service doesn't get exposed anymore.
My configuration is the following:

    server.port: {{ .Values.httpServerPort }}
    spring:
      main.banner-mode: off
      grpc:
        server:
          port: {{ .Values.grpcServerPort }}
          health.actuator.health-indicator-paths:
            - liveness
            - readiness

In the logs of my application I can see:

{"@timestamp":"2026-03-02T12:07:25.589Z","log.level": "INFO","message":"Registered gRPC service: timekeepers.timeseriesapi.v1.TimeSeriesService","ecs.version": "1.2.0","service.name":"TimeSeries API","service.version":"0.0.5-SNAPSHOT","service.environment":"dev","event.dataset":"timeseries-api","process.thread.name":"main","log.logger":"org.springframework.grpc.server.NettyGrpcServerFactory","event.kind":"event"}
{"@timestamp":"2026-03-02T12:07:25.589Z","log.level": "INFO","message":"Registered gRPC service: grpc.reflection.v1.ServerReflection","ecs.version": "1.2.0","service.name":"TimeSeries API","service.version":"0.0.5-SNAPSHOT","service.environment":"dev","event.dataset":"timeseries-api","process.thread.name":"main","log.logger":"org.springframework.grpc.server.NettyGrpcServerFactory","event.kind":"event"}
{"@timestamp":"2026-03-02T12:07:25.609Z","log.level": "INFO","message":"gRPC Server started, listening on address: [/[0:0:0:0:0:0:0:0]:29090]","ecs.version": "1.2.0","service.name":"TimeSeries API","service.version":"0.0.5-SNAPSHOT","service.environment":"dev","event.dataset":"timeseries-api","process.thread.name":"main","log.logger":"org.springframework.grpc.server.lifecycle.GrpcServerLifecycle","event.kind":"event"}
{"@timestamp":"2026-03-02T12:07:25.659Z","log.level": "INFO","message":"Started TimeSeriesApiApplication in 5.802 seconds (process running for 6.311)","ecs.version": "1.2.0","service.name":"TimeSeries API","service.version":"0.0.5-SNAPSHOT","service.environment":"dev","event.dataset":"timeseries-api","process.thread.name":"main","log.logger":"com.foo.cit.fmd.timekeepers.timeseriesapi.TimeSeriesApiApplication","event.kind":"event"}

but no entry for the service grpc.health.v1.Health.

Moreover, trying to calling it results in an error as well:

cdprete@myhost:~> grpcurl grpc-timeseries-api-timekeepers-hiku.ingress.ocp.foo.net:443 grpc.health.v1.Health/Check
Error invoking method "grpc.health.v1.Health/Check": target server does not expose service "grpc.health.v1.Health"

[cdprete]

It seems that

static class OnHealthDefaultEnablementCondition extends SpringBootCondition {

		@Override
		public ConditionOutcome getMatchOutcome(ConditionContext context, AnnotatedTypeMetadata metadata) {
			String propertyName = "spring.grpc.server.health.enabled";
			BindResult<Boolean> enabled = Binder.get(context.getEnvironment()).bind(propertyName, Boolean.class);
			if (enabled.isBound()) {
				return enabled.get() ? ConditionOutcome.match("Health explicitly enabled")
						: ConditionOutcome.noMatch("Health explicitly disabled");
			}
			if (context.getBeanFactory() == null) {
				return ConditionOutcome.noMatch("Context bean factory is null");
			}
			String[] bindableServices = context.getBeanFactory()
				.getBeanNamesForType(BindableService.class, false, false);
			return (bindableServices.length > 0) ? ConditionOutcome.match("BindableService found")
					: ConditionOutcome.noMatch("No BindableService found and health not explicitly enabled");
		}

	}

gets evaluated too early and the array of bindableServices is empty.
I also tried to change my configuration as follows

@Configuration(proxyBeanMethods = false)
@AutoConfigureBefore(GrpcServerHealthAutoConfiguration.class)
public class EndpointFacadeGrpcConfiguration {

    @GrpcService(interceptors = MdcGrpcServerInterceptor.class)
    EndpointFacadeGrpc endpointFacadeGrpc(OnlineSpaceEndpoint onlineSpaceEndpoint,
                                          DeltaSpaceEndpoint deltaSpaceEndpoint) {
        return new EndpointFacadeGrpc(onlineSpaceEndpoint, deltaSpaceEndpoint);
    }
}

but the hint about the order is simply ignored.

Moreover, the issue happens also when not running in AOT.

[cdprete]

Even by explicitly enabling it with

spring.grpc.server.health:
  enabled: true
  actuator.health-indicator-paths:
    - liveness
    - readiness

it seems to not be working since OCP can't reach those probes:

[therepanic]

Thanks for reporting this, @cdprete. I have some thoughts on this matter. I think it's worth looking at the bean registry, not the currently existing ones, as I did in spring-projects/spring-grpc@15e5372. I'll send a PR soon; I have some ideas.

[therepanic]

I think I figured out the problem and attached the PR spring-projects/spring-grpc#381, PTAL.

[cdprete]

Please be aware that it's not working even when it's explicitly enabled. I don't know if the fix provided covers this case as well. Il mar 3 mar 2026, 14:15 Andrey Litvitski ***@***.***> ha scritto:

…

*therepanic* left a comment (spring-projects/spring-boot#49830) <#49830 (comment)> I think I figured out the problem and attached the PR spring-projects/spring-grpc#381 <spring-projects/spring-grpc#381>, PTAL. — Reply to this email directly, view it on GitHub <#49830 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACAZGWHQDJR2QWROAV7CHGT4O3LFRAVCNFSM6AAAAACWFC2NICVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTSOJRGAYTKMBYGI> . You are receiving this because you were mentioned.Message ID: ***@***.***>

[cdprete]

Hello @therepanic.

What's the state on this?

@dsyer @onobc can we have this fixed? In my OCP environment I'm currently forced to have 2 servers running (HTTP + gRPC) just to expose the probes from the HTTP one since the gRPC health is not accessible anymore.

[cdprete]

@dsyer what's the timeline for the Spring Boot migration?

I can understand postponing new features, but bug fixes doesn't sound reasonable to me, unless you say it will happen very soon.

[dsyer]

It already happened. Spring gRPC main is now independent of Spring Boot. I'll see if we can transfer some issues automatically to Spring Boot.

[philwebb]

Transferred issue from spring-grpc to spring-boot. We will triage this issue against the updated codebase in due course.

[cdprete]

Transferred issue from spring-grpc to spring-boot. We will triage this issue against the updated codebase in due course.

Hi @philwebb.

In which version of Spring Boot I can expect this to be solved?