Open DebajitKumarPhukan opened 1 year ago
The probe command has to an application not just shell command.
spring.cloud.deployer.kubernetes.liveness-command-probe-command='/bin/sh -c "echo live"'
spring.cloud.deployer.kubernetes.probe-type=COMMAND
@corneil Hi, thanks for attending to this issue. I already tried all the possible combinations (including the ones you mentioned). The main issue here is that the pod yaml specifications generated don't have readiness or liveness specifications when probe-type = COMMAND and even if you specify liveness-command-probe-command or readiness-command-probe-command (in any ways).
@corneil Any updates ?
Issue: I have implemented a Spring Batch application which applies remote partitioning and launches jobs in Kubernetes. The issue I identified was that when I attempted for a command based readiness and liveness probe, it doesn't seem to be working at all. I verified the same in pod yaml and can't see any readiness/liveness probe generated at all. I can only see them passed under
spec.containers.args
in pod yaml.Below are the configs I specified in the application.properties
I even tried setting below config with the hope that it would resolve the issue, but unfortunately it didn't.
spring.cloud.deployer.kubernetes.probe-type=command