Package version:
Optional failureMinimum consecutive failures for the probe to be considered failed after having succeeded. Defaults to 3. Minimum value is 1. Maximum value is 10.
Optional httpHTTPGet specifies the http request to perform.
Optional initialNumber of seconds after the container has started before liveness probes are initiated. Minimum value is 1. Maximum value is 60.
Optional periodHow often (in seconds) to perform the probe. Default to 10 seconds. Minimum value is 1. Maximum value is 240.
Optional successMinimum consecutive successes for the probe to be considered successful after having failed. Defaults to 1. Must be 1 for liveness and startup. Minimum value is 1. Maximum value is 10.
Optional tcpTCPSocket specifies an action involving a TCP port. TCP hooks not yet supported.
Optional terminationOptional duration in seconds the pod needs to terminate gracefully upon probe failure. The grace period is the duration in seconds after the processes running in the pod are sent a termination signal and the time when the processes are forcibly halted with a kill signal. Set this value longer than the expected cleanup time for your process. If this value is nil, the pod's terminationGracePeriodSeconds will be used. Otherwise, this value overrides the value provided by the pod spec. Value must be non-negative integer. The value zero indicates stop immediately via the kill signal (no opportunity to shut down). This is an alpha field and requires enabling ProbeTerminationGracePeriod feature gate. Maximum value is 3600 seconds (1 hour)
Optional timeoutNumber of seconds after which the probe times out. Defaults to 1 second. Minimum value is 1. Maximum value is 240.
Optional typeThe type of probe.
Generated using TypeDoc
Probe describes a health check to be performed against a container to determine whether it is alive or ready to receive traffic.