Facility Deprecation

[displague]

How to categorize this issue?

/area control-plane
/kind api-change

/platform equinix-metal

What would you like to be added:

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

Why is this needed:

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).

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

Code of interest:

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

related to:

• Support for Metros and (multiple) Facilities #161
• Facility Deprecation machine-controller-manager-provider-equinix-metal#16
• Deprecate Facility provisioning parameters equinixmetal-archive/packngo#369