Add Health Probes to your service
By default, Ingress controller will provision an HTTP GET probe for the exposed pods.
The probe properties can be customized by adding a Readiness or Liveness Probe to your deployment
/pod
spec.
With readinessProbe
or livenessProbe
apiVersion: networking.k8s.io/v1
kind: Deployment
metadata:
name: aspnetapp
spec:
replicas: 3
template:
metadata:
labels:
service: site
spec:
containers:
- name: aspnetapp
image: mcr.microsoft.com/dotnet/samples:aspnetapp
imagePullPolicy: IfNotPresent
ports:
- containerPort: 80
readinessProbe:
httpGet:
path: /
port: 80
periodSeconds: 3
timeoutSeconds: 1
Kubernetes API Reference:
Note
readinessProbe
andlivenessProbe
are supported when configured withhttpGet
.- Probing on a port other than the one exposed on the pod is currently not supported.
HttpHeaders
,InitialDelaySeconds
,SuccessThreshold
aren't supported.
Without readinessProbe
or livenessProbe
If the above probes aren't provided, then the Ingress Controller makes an assumption that the service is reachable on the Path
specified for backend-path-prefix
annotation, or the path
specified in the ingress
definition for the service.
Default Values for Health Probe
For any property that can't be inferred by the readiness/liveness probe, default values are set.
Application Gateway Probe Property | Default Value |
---|---|
Path |
/ |
Host |
localhost |
Protocol |
HTTP |
Timeout |
30 |
Interval |
30 |
UnhealthyThreshold |
3 |
Feedback
https://aka.ms/ContentUserFeedback.
Coming soon: Throughout 2024 we will be phasing out GitHub Issues as the feedback mechanism for content and replacing it with a new feedback system. For more information see:Submit and view feedback for