Skip to content
This repository was archived by the owner on Aug 12, 2025. It is now read-only.

Commit 2f4c642

Browse files
committed
docs: More updates to facility warning
Signed-off-by: Chris Privitere <[email protected]>
1 parent e8c2905 commit 2f4c642

File tree

1 file changed

+2
-2
lines changed

1 file changed

+2
-2
lines changed

README.md

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -18,8 +18,8 @@ This is the official [cluster-api](https://github.com/kubernetes-sigs/cluster-ap
1818
* Facility is still usable, but should be moved away from as soon as you can
1919
* See here for more info on the facility deprecation: [Bye Facilities, Hello (again) Metros](https://feedback.equinixmetal.com/changelog/bye-facilities-hello-again-metros)
2020
* If you would like to upgrade your existing clusters from using facilities to using metros, please work with your Equinix support team to figure out the best course of action. We can also provide some support via our [community Slack](https://slack.equinixmetal.com/) and the [Equinix Helix community site](https://community.equinix.com/).
21-
* The basic requirement will be to replace `facility: sv15` with `metro: sv` (insert your correct metro instead of sv, for more information check out our [Metros documentation](https://deploy.equinix.com/developers/docs/metal/locations/metros/)) in your existing PacketCluster and PacketMachine objects and/or yaml files used to reconcile those objects (if you're say, managing them via GitOps)
22-
* The expectation is that if the devices are already in the correct metros you've specified, no disruption will happen to clusters or their devices.
21+
* The basic process will be to upgrade to v0.7.0, then replace `facility: sv15` with `metro: sv` (insert your correct metro instead of sv, for more information check out our [Metros documentation](https://deploy.equinix.com/developers/docs/metal/locations/metros/)) in your existing PacketCluster and PacketMachine objects and/or yaml files used to reconcile those objects (if you're say, managing them via GitOps)
22+
* The expectation is that if the devices are already in the correct metros you've specified, no disruption will happen to clusters or their devices, however, **as with any breaking change you should verify this outside of production before you upgrade.**
2323

2424
## Requirements
2525

0 commit comments

Comments
 (0)