-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
✨ Add Metro Support #313
Comments
I think it should be handle the same as the CPEM. It seems like the first choice is Facility, and if a Facility isn't defined it falls back to Metro, if also no Metro is defined it results in an error. |
The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs. This bot triages issues and PRs according to the following rules:
You can:
Please send feedback to sig-contributor-experience at kubernetes/community. /lifecycle stale |
/remove-lifecycle stale |
Sounds like we've decided facility and metro should be mutually exclusive arguments where one is required. |
User Story
Support metro based provisioning. https://metal.equinix.com/developers/docs/locations/metros/
2023-05-01 Update (MJ): see also https://feedback.equinixmetal.com/changelog/bye-facilities-hello-again-metros
Detailed Description
As information becomes available this description will be updated and comments will be added to support the implementation changes.
Documentation should be broadly updated to demonstrate metros. A few smaller examples can demonstrate Facilities.
/kind feature
From a recent discussion on Slack/Zoom with Moath on the K8S Slack, these talking points came up:
Tasks
The text was updated successfully, but these errors were encountered: