chore: update to CCM 3.0.1

[rawkode]

What this PR does / why we need it:

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 #

[rawkode]

/assign @detiber

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: displague, rawkode
To complete the pull request process, please ask for approval from detiber after the PR has been reviewed.

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

[displague]

@rawkode perhaps we should update this to https://github.com/equinix/cloud-provider-equinix-metal/releases/tag/v3.1.0

[detiber]

@displague I can also handle that as a followup, I'm working on verifying things related to upgrades with updating to a newer version of the CCM

[deitch]

Is there a reason we are pulling from raw.githubusercontent.com (ie from the tree) and not from the releases section? I guess it doesn't really matter - both pull down the same content - but isn't releases the "official" place to go?

[displague]

@deitch makes a good point. The releases are build artifacts that we can update if needed. While that may be bad practice, especially without reporting the checksums, this does offer a way to fix bad past releases. Pinning to tags does not allow that (unless we force-move the tag 😬 )

[k8s-triage-robot]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually close.

If this issue is safe to close now please do so with /close.

Send feedback to sig-contributor-experience at kubernetes/community.
/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[detiber]

Closing in favor of #269, which includes additional fixes and migration tooling needed to properly upgrade the CCM
/close

[k8s-ci-robot]

@detiber: Closed this PR.

In response to this:

Closing in favor of #269, which includes additional fixes and migration tooling needed to properly upgrade the CCM
/close

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.