You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Sometimes, you have to deal with legacy applications that might require an additional startup time on their first initialization.
The application will have a maximum of 5 minutes (30 * 10 = 300s) to finish its startup.
Once the startup probe has succeeded once, the liveness probe takes over to provide a fast response to container deadlocks.
If the startup probe never succeeds, the container is killed after 300s and subject to the pod's restartPolicy.
Step-03: Review Startup Probe YAML
File Name: 05-UserMgmtWebApp-Deployment.yaml
# Startup Probe - Wait for 5 minutes till the application starts startupProbe:
httpGet:
path: /loginport: 8080initialDelaySeconds: 60periodSeconds: 10failureThreshold: 30# The application will have a maximum of 5 minutes (30 * 10 = 300s) to finish its startup.successThreshold: 1# Default value
Step-04: Deploy Kubernetes Manifests
# Deploy Kubernetes Manifests
kubectl apply -f kube-manifests-startup-probe
# List Pods
kubectl get pods
Observation:
# List Services
kubectl get svc
# Access Application
http://<LB-IP>
Username: admin101
Password: password101