Skip to content

add How_to_add_healthcheck_for_acp_clusters.md #56

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
fanzy618 merged 1 commit into from
Sep 9, 2025
Merged

add How_to_add_healthcheck_for_acp_clusters.md #56

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
22 changes: 22 additions & 0 deletions docs/en/solutions/How_to_add_healthcheck_for_acp_clusters.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,22 @@
---
products:
- Alauda Container Platform
kind:
- Solution
---
# How to add a health check for ACP clusters
## Overview
The ALB health check port, which is pre-installed in each cluster, serves as an endpoint for monitoring cluster health status. If this port becomes inaccessible, it indicates that the cluster is in an unhealthy state.
## Prerequisites
When utilizing the ALB health check port for cluster health monitoring in a VIP-based access configuration, it is mandatory to set up port forwarding rules on the Virtual IP (VIP) for the designated health check port. Failure to configure this port forwarding will result in non-functional health checks.
## Config Vip Health Check
The following table specifies the required configuration parameters for Virtual IP (VIP) health check implementation:

| Health Check Parameters | Description |
| -------- | -------- |
| Address | the address of ALB |
| Port | 11782 |
| Protocol | The protocol type of the health check, it is recommended to use TCP. |
| Response Timeout | The time required to receive the health check response, it is recommended to configure it to 2 seconds. |
| Check Interval | The time interval for the health check, it is recommended to configure it to 5 seconds. |
| Unhealthy Threshold | The number of consecutive failures after which the health check status of the backend server is determined to be failed, it is recommended to configure it to 3 times. |