Facility Deprecation

[displague]

What happened:

Equinix Metal is deprecating facility deployment. Metros encompass multiple facilities and are a better fit for availability concerns.

Metro provisioning is largely implemented in the same way, whether for IP addresses, VLANs, or Metal servers. The metro field is supplied instead of the facility (or facilities) field. The response object will include a metro rather than (in some cases, in addition to) a facility field. Network resources previously configured in a facility are available within the metro that facility resides within. All previously 'facility' provisioned network resources are portable across the metro with respect to the Metal Project (which has always been a secondary context for network resources).

What you expected to happen:

The provider should more completely adapt to Metro based provisioning and remove Facility deployment options.

How to reproduce it (as minimally and precisely as possible):

Anything else we need to know:

https://feedback.equinixmetal.com/changelog/bye-facilities-hello-again-metros

Code of interest:

• https://github.com/search?q=repo%3Agardener%2Fmachine-controller-manager-provider-equinix-metal%20ewr1&type=code
• https://github.com/search?q=repo%3Agardener%2Fmachine-controller-manager-provider-equinix-metal%20facilities&type=code

Environment:

Equinix Metal

• related to Support for Metros and (multiple) Facilities gardener-extension-provider-equinix-metal#161
• Facility Deprecation gardener-extension-provider-equinix-metal#265
• Deprecate Facility provisioning parameters equinixmetal-archive/packngo#369