🐛 Fix timeout handling in GetAPIServerCertificateExpiry and DialContext

[LingyanCao]

What this PR does / why we need it:
This PR adds proper timeout handling to prevent hanging connections when getting API server certificate expiry. The changes include:

• Add 15-second timeout using context.WithTimeoutCause() in GetAPIServerCertificateExpiry()
• Handle context timeout in DialContext() by configuring HTTP client timeout based on context deadline
• Add early context cancellation checks to fail fast when context is already cancelled

These changes prevent indefinite blocking during certificate expiry checks and improve debugging with descriptive timeout errors.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #12460

area/provider/control-plane-kubeadm

[k8s-ci-robot]

@LingyanCao: The label(s) area/kubeadm cannot be applied, because the repository doesn't have them.

In response to this:

What this PR does / why we need it:
This PR adds proper timeout handling to prevent hanging connections when getting API server certificate expiry. The changes include:

• Add 15-second timeout using context.WithTimeoutCause() in GetAPIServerCertificateExpiry()
• Handle context timeout in DialContext() by configuring HTTP client timeout based on context deadline
• Add early context cancellation checks to fail fast when context is already cancelled

These changes prevent indefinite blocking during certificate expiry checks and improve debugging with descriptive timeout errors.

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #12460

/area kubeadm

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-sigs/prow repository.

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: LingyanCao (b2aca38)

[k8s-ci-robot]

Welcome @LingyanCao!

It looks like this is your first PR to kubernetes-sigs/cluster-api 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/cluster-api has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @LingyanCao. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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-sigs/prow repository.

[sbueringer]

@LingyanCao PTAL at the CLA: #12554 (comment)

[sbueringer]

/ok-to-test

[sbueringer]

/test pull-cluster-api-e2e-main-gke

[sbueringer]

/test pull-cluster-api-e2e-main-gke

Error is unrelated

[sbueringer]

Change lgtm. I would merge as soon as the CLA is done

[sbueringer]

I think this will also fix cases where etcd requests got stuck.

@fabriziopandini This might fix some of our resourceVersion not stable flakes with KCP

[sbueringer]

Thank you!

/test pull-cluster-api-e2e-main-gke
/lgtm
/approve

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: sbueringer

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

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [sbueringer]

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

[k8s-ci-robot]

LGTM label has been added.

Git tree hash: b859ee8c190a7f14990733482ecaf7deb243f665