Increase liveness probe initial delay for Keycloak and Che server to prevent failure in case of longer start (#647)
Signed-off-by: Mykola Morhun <mmorhun@redhat.com>pull/649/head
parent
8c6d70d909
commit
a4da381730
|
|
@ -625,7 +625,7 @@ func GetSpecKeycloakDeployment(
|
|||
Port: intstr.FromInt(8080),
|
||||
},
|
||||
},
|
||||
InitialDelaySeconds: 90,
|
||||
InitialDelaySeconds: 300,
|
||||
FailureThreshold: 10,
|
||||
TimeoutSeconds: 5,
|
||||
PeriodSeconds: 10,
|
||||
|
|
|
|||
|
|
@ -352,7 +352,7 @@ func GetSpecCheDeployment(deployContext *deploy.DeployContext) (*appsv1.Deployme
|
|||
},
|
||||
},
|
||||
// After POD start, don't initiate liveness probe while the POD is still expected to be declared as ready by the readiness probe
|
||||
InitialDelaySeconds: 200,
|
||||
InitialDelaySeconds: 400,
|
||||
FailureThreshold: 3,
|
||||
TimeoutSeconds: 3,
|
||||
PeriodSeconds: 10,
|
||||
|
|
|
|||
Loading…
Reference in New Issue