[e2e] error: failed to get component source YAML

### Which jobs are failing?

periodic-cluster-api-e2e-upgrade-1-31-1-32-release-1-11
periodic-cluster-api-e2e-conformance-ci-latest-release-1-11
periodic-cluster-api-e2e-conformance-ci-latest-main
periodic-cluster-api-e2e-conformance-ci-latest-release-1-12
periodic-cluster-api-e2e-upgrade-1-32-1-33-release-1-12

### Which tests are failing?

  | capi-e2e [SynchronizedBeforeSuite]
-- | --

### Since when has it been failing?

Feb 4 2026

### Testgrid link

https://storage.googleapis.com/k8s-triage/index.html?text=failed%20to%20get%20component%20source%20YAML%20from%20URL&job=.*cluster-api&xjob=.*-provider-

### Reason for failure (if possible)

failed to get component source YAML from URL: failed to get https://github.com/kubernetes-sigs/cluster-api/releases/download/v1.10.10/bootstrap-components.yaml: got status code 502

Loading this file from browser works fine

### Anything else we need to know?

Loading this file from browser works fine

### Label(s) to be applied

/kind failing-test
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

Start at the capi-e2e SynchronizedBeforeSuite setup and reproduce the failing jobs while fetching bootstrap-components.yaml from the release URL. Determine whether the 502 can be reproduced and identify the expected handling for this failed download. Done means the affected e2e jobs reliably complete or the failure is reported with a clear, actionable cause.

Written by the indexing model from the issue text.