Cluster-API-Provider-Packet v0.7.0 Release
Version 0.7.0 of cluster-api-provider-packet, introduces metro level support vs facility level in accordance with the soon-to-be updated Metal API. Users ofprevious versions will want to take advantage of this immediately. The basic requirements to upgrade your existing clusters can be found here. Please work with your Equinix support team to determine the best migration path for your architecture. Assistance can also be found in theCommunity Slack andCommunity site. Read more at our Metros Quick Reference and see the facility deprecation announcement. *Please note that if devices are already in the correct metros you’ve specified, no disruption will happen to clusters or their devices. As with any production change, test your changes before applying them to clusters in production. In addition to metro-level support, this release installs the latestcloud-provider-equinix-metal v3.6.1 by default and is built on golang version 1.19 and cluster-api 1.3. The default OS used is Ubuntu 20.04 and kube-vip is updated to v0.5.12 in the kube-vip flavor templates. Lastly, the CI workflow has been refactored with caching removed and updated tests considering cluster-api 1.3 dependencies. See more at the github release here! https://github.com/kubernetes-sigs/cluster-api-provider-packet/releases/tag/v0.7.0Nutanix Examples: Protection Policy with VM Migration & Active Directory Authentication
Those looking to explore Nutanix on Equinix Metal are likely to have two concerns in mind: ease of migration and security. Thankfully, two examples have recently been added to the Equinix Terraform directory that demonstrate exactly how a user can accomplish these two things. Nutanix Clusters Setup and Protection Policy - walks a user through creating two Nutanix Clusters on Equinix Metal rapidly, create a protection policy between them, and then practice creating a VM in one cluster and migrating it to the other cluster. Nutanix on Equinix Metal with Active Directory Authentication - helps a user create a cluster on Equinix, add an AD server VM, configure AD authentication, and map a few sample roles to the AD. Both examples use a combination of Terraform and manual Prism console steps, promoting understanding while deploying with speed and convenience. Consider walking through these examples if you're interested in exploring Nutanix on Equinix Metal or learning more about making your infrastructure more reliable and secure.How a Self-Taught Coder Helped Istio Solve Cloud Native Networking
Managing network connections for an application used to be relatively straight forward. Applications were written and run as monoliths and didn’t need internal connectivity to integrate their constituent parts. And there weren't a whole lot of resources they needed to connect to externally. Read the full Blog Here!How to Add SSH Public Keys to the Metal Console
In this video, we'll show you how to add SSH Public Keys to the Metal Console. We'll start with a breakdown of the Equinix Metal organizational structure — explaining the difference between signing up as an individual or through an invitation. Then we'll head to the Metal Console and add a new Public SSH Key to our profile. Then we'll create a User Key that can be used across multiple projects and organizations. Next we'll deploy a new on-demand server to see how it interacts with the project and user keys. The SSH Keys tab is under the Optional Settings section and we'll find the newly created project and user keys.
OpenShift on Baremetal v0.5.0
A Terraform module that quickly installs OpenShift for use on Equinix Metal. First off, v0.4.0 aligned with thesupport of metros and deprecated the use of facilities; see the announcement here. The default location was changed fromSJC1 to DA, the default size is c3.small vs the previous c2.medium, and Terraform version 1 or higher isrequired. Underlying this is also a switch from our Metal specific Terraform provider to the full Equinix Terraform provider (v.1.14.1). This allows more configurability for node plans and better default node plans. Newer versions of OpenShift are used. This also includes several outstanding bug and CI fixes that were preventing the project from successfully functioning.It is recommended to rebuild any existing deployments. Migration should be possible by converting the state files as described in theMigrating from equinix/metal to equinix/equinix. v0.5.0 does all the above but includes minor update to the install instructions and provides us with module_name visibility that we use to gauge usage as an indicator of audience value.
