You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Equinix recently (25th November 2024) announced they are sunsetting their Equinix metal offering by July 2026. Since this WG relies on the offering, we need to evaluate how this affects us.
Is it an option to stay with Equinix?: Our setup can also be run on other Equinix offerings? We need access to low-level metrics for utilization and energy measurements (@rossf7 and others know things in detail). Maybe @vielmetti knows things 😄
Move platform: @krook we likely need to move platforms. Since we are running on CNCF provided infrastructure; is there an option to evaluate other platforms. Hetzner, for example, could be another option.
Thanks @leonardpahlke , happy to work through options on this. We have been coordinating with @jeefy on the CNCF logistics. A lot of details are TBD but the more you can relate specific requirements the easier it will be to figure out what is a good match.
Our requirements mainly come from Kepler. So with bare metal we're measuring with RAPL and not in estimation mode. We're using x86 but I believe ARM with Ampere is also an option but I haven't tried that yet!
For provisioning we use OpenTofu and then K3s and Cilium. So if there is a compatible provider we could use that would be helpful.
Thanks Ed and Leo 🙌 I hope that helps with requirements. Let me know if you need more details.
@leonardpahlke FYI, we’re working with the Equinix Metal (@vielmetti) team closely on the further plan. No need to worry at this point of time, as the current operations remain unaffected.
Hello all,
Equinix recently (25th November 2024) announced they are sunsetting their Equinix metal offering by July 2026. Since this WG relies on the offering, we need to evaluate how this affects us.
Links:
cc @nikimanoledaki @AntonioDiTuri
@krook I will open a service desk ticket regarding this topic!
Thanks, all! 🙌
The text was updated successfully, but these errors were encountered: