Configuring/Adjusting Readiness Probes for Containers

Configuring/Adjusting Readiness Probes for Containers

Overview:

Readiness probes are critical in container orchestration to ensure that containers are ready to handle traffic before they are included in service load balancing. If a container fails readiness probes due to insufficient thresholds, adjusting these parameters can help. This guide explains how to modify readiness probe settings to accommodate containers with longer startup times.

Key Readiness Probe Parameters:

1. initialDelaySeconds: Delay before the first probe is initiated after the container starts.
2. periodSeconds: Interval between successive probes.
3. timeoutSeconds: Maximum duration a probe can take before it is considered failed.
4. failureThreshold: Number of consecutive failures allowed before the container is marked as unready.

Recommended Configuration:

To give the container more time to become available, the following settings can be adjusted:

readinessProbe:
  failureThreshold: 5         # Allows more failures before marking the container as unready
  httpGet:
    path: /
    port: metrics
    scheme: HTTP
  initialDelaySeconds: 30     # Provides 30 seconds before the first readiness probe
  periodSeconds: 10           # Reduces the frequency of checks to every 10 seconds
  successThreshold: 1         # Default, the number of successes needed to mark the container as ready
  timeoutSeconds: 20          # Increases the time allowed for the probe to complete

Implementation:

To apply these changes to your deployment, follow these steps:

Access the Deployment's Edit Mode:

kubectl -n sisense edit deployment <deployment_name>

1. Replace <deployment_name> with the name of your specific deployment.
2. Navigate to the readinessProbe Section: Scroll through the deployment configuration until you find the readinessProbe section. Adjust the parameters as needed, based on the recommended configuration above.
3. Save Changes and Exit Edit Mode: After making the necessary adjustments, save the file and exit the edit mode. The deployment will automatically restart, applying the new readiness probe configuration.

Conclusion:

Proper configuration of readiness probes ensures that only containers ready to handle traffic are included in service routing. Adjusting initialDelaySeconds, periodSeconds, timeoutSeconds, and failureThreshold helps to manage containers with longer startup times effectively. By following the implementation steps, you can easily modify the probe settings and enhance the stability and reliability of your deployments.