Consider cluster domain when draining capture servers across multiple kubernetes clusters

[charleszheng44]

What problem does this PR solve?

When deploying TiCDC cluster containing capture servers managed by different tidb cluster CRs across multiple Kubernetes clusters. In this case, the existing tidb operator won't be able to pick the right capture to drain, as two caputre servers may share similar advertise address prefix.

What is changed and how does it work?

Consider cluster domain when draining capture servers across multiple kubernetes clusters

Code changes

• Has Go code change
• Has CI related scripts change

Tests

• Unit test
• E2E test
• Manual test
• No code

Side effects

• Breaking backward compatibility
• Other side effects:

Related changes

• Need to cherry-pick to the release branch
• Need to update the documentation

Release Notes

Please refer to Release Notes Language Style Guide before writing the release note.

`None`

[ti-chi-bot]

@overvenus: adding LGTM is restricted to approvers and reviewers in OWNERS files.

In response to this:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ti-chi-bot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: overvenus
Once this PR has been reviewed and has the lgtm label, please ask for approval from charleszheng44. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[charleszheng44]

LGTM

[charleszheng44]

/test all

[ti-chi-bot]

@charleszheng44: No presubmit jobs available for pingcap/tidb-operator@master

In response to this:

/test all

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[charleszheng44]

/test pull-e2e-kind

[ti-chi-bot]

@charleszheng44: No presubmit jobs available for pingcap/tidb-operator@master

In response to this:

/test pull-e2e-kind

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[wuhuizuo]

/run-e2e-kind-br

[charleszheng44]

/run-all-e2e

[charleszheng44]

/merge

[charleszheng44]

/run-e2e-kind

[codecov-commenter]

Codecov Report

Merging #5040 (f7d8a5e) into master (2da77b8) will decrease coverage by 0.01%.
The diff coverage is 100.00%.

Additional details and impacted files

@@            Coverage Diff             @@
##           master    #5040      +/-   ##
==========================================
- Coverage   57.24%   57.24%   -0.01%     
==========================================
  Files         245      245              
  Lines       28069    28072       +3     
==========================================
+ Hits        16069    16070       +1     
- Misses      10435    10436       +1     
- Partials     1565     1566       +1     

Flag	Coverage Δ
unittest	57.24% <100.00%> (-0.01%)	⬇️

[charleszheng44]

/run-e2e-kind-tngm

[charleszheng44]

/run-e2e-kind-br

[charleszheng44]

/cherry-pick release-1.4

[charleszheng44]

/cherry-pick release-1.5

[wuhuizuo]

/cherry-pick release-1.4

[wuhuizuo]

/cherry-pick release-1.4
/cherry-pick release-1.5

[ti-chi-bot]

@wuhuizuo: The label(s) /release-1.4, /release-1.5 cannot be applied, because the repository doesn't have them.

In response to this:

/cherry-pick release-1.4
/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[wuhuizuo]

/cherry-pick release-1.4

[ti-chi-bot]

@wuhuizuo: The label(s) /release-1.4 cannot be applied, because the repository doesn't have them.

In response to this:

/cherry-pick release-1.4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

@wuhuizuo: new pull request created to branch release-1.4: #5042.

In response to this:

/cherry-pick release-1.4
/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

@wuhuizuo: new pull request could not be created: failed to create pull request against pingcap/tidb-operator#release-1.4 from head ti-chi-bot:cherry-pick-5040-to-release-1.4: status code 422 not one of [201], body: {"message":"Validation Failed","errors":[{"resource":"PullRequest","code":"custom","message":"A pull request already exists for ti-chi-bot:cherry-pick-5040-to-release-1.4."}],"documentation_url":"https://docs.github.com/rest/reference/pulls#create-a-pull-request"}

In response to this:

/cherry-pick release-1.4

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.

[ti-chi-bot]

@wuhuizuo: new pull request created to branch release-1.5: #5043.

In response to this:

/cherry-pick release-1.4
/cherry-pick release-1.5

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the ti-community-infra/tichi repository.