use dl.k8s.io instead of hardcoded GCS URIs

[spiffxp]

Use dl.k8s.io instead of hardcoded GCS URIs

What type of PR is this?

/kind cleanup

What this PR does / why we need it:

The only time a kubernetes GCS bucket name should be showing up in a
hardcoded URI is if gsutil is being used (e.g. gsutil cp gs://foo/bar .)

Otherwise, for tools like curl or wget, dl.k8s.io is much nicer for us
as a project, since we can transparently change where that redirects to
without having to change code everywhere

These changes will mean no changes will be necessary to accommodate a
gs://kubernetes-release -> gs://k8s-release migration equivalent of
the CI migration we're going through right now

These changes also address the gs://kubernetes-release-dev references
currently used by this repo (ref:
kubernetes/k8s.io#2318)

Special notes for your reviewer:

I'm not sure that a release note is required for this, but I put one in
just in case

Similar / related PRs:

• Use dl.k8s.io instead of hardcoded GCS URIs image-builder#656
• 🌱 Use dl.k8s.io instead of hardcoded GCS URIs cluster-api#4958

TODOs:

• squashed commits
• includes documentation (n/a)
• adds unit tests (n/a)

Release note:

kubernetes artifacts are pulled from https://dl.k8s.io instead of
hardcoded GCS bucket URIs (kubernetes-release, kubernetes-release-dev)

[cpanato]

/test ls

[k8s-ci-robot]

@cpanato: The specified target(s) for /test were not found.
The following commands are available to trigger jobs:

• /test pull-cluster-api-provider-gcp-test
• /test pull-cluster-api-provider-gcp-build
• /test pull-cluster-api-provider-gcp-make
• /test pull-cluster-api-provider-gcp-e2e-test
• /test pull-cluster-api-provider-gcp-make-conformance
• /test pull-cluster-api-provider-gcp-capi-e2e

Use /test all to run the following jobs:

• pull-cluster-api-provider-gcp-test
• pull-cluster-api-provider-gcp-build
• pull-cluster-api-provider-gcp-make
• pull-cluster-api-provider-gcp-e2e-test

In response to this:

/test ls

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.

[cpanato]

/test pull-cluster-api-provider-gcp-make-conformance

[cpanato]

thanks Aaron
/approve
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: cpanato

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 [cpanato]

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