support multiple health checkers per cluster

[wbpcode]

Title: support multiple health checkers per cluster

Description:
This is a very old issue. I happened to be doing some related work recently, so I am trying to see if I can close this issue. Here is some simple design.

[optional Relevant Links:]

#3642

we are running into this same issue, it appears both api v2 and api v3 accept multiple health checks, but envoy itself does not support them

[wbpcode]

API: The Health Checkers for the Upstream Cluster currently provided by the community is an array that can accept multiple Health Checkers, so the API can be reused directly without redesign. In the initial design, if any Health Checker fails, the Host is marked as unhealthy. Multiple Health Checkers work independently of each other and are identified with a unique ID.

Record: An additional Flag will be used to record which Health Checker has set the status of the Host. For example, each bit represents a Health Checker.

Status Update:

• If Health Checker X considers the status of Host A to be healthy:
  • If the previous status of A is healthy: Do nothing.
  • If the previous status of A is unhealthy: Clear Flag set by X. If Flag == 0, then update status of A to be healthy.
• If Health Checker X considers the status of Host A to be unhealthy:
  • If the previous status of A is healthy: Set Flag and update status of A to be unhealthy.
  • If the previous status of A is unhealthy: Set Flag.

[antoniovicente]

Is this a duplicate of #3642 ?

[wbpcode]

Is this a duplicate of #3642 ?

This is a reply to #3642 and I will create a PR that used to close #3642.

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[wbpcode]

/no-stale

[github-actions]

This issue has been automatically marked as stale because it has not had activity in the last 30 days. It will be closed in the next 7 days unless it is tagged "help wanted" or "no stalebot" or other activity occurs. Thank you for your contributions.

[github-actions]

This issue has been automatically closed because it has not had activity in the last 37 days. If this issue is still valid, please ping a maintainer and ask them to label it as "help wanted" or "no stalebot". Thank you for your contributions.