Go SDK | Inside Equinix Developer Tech
In this video, David Flanagan, a.k.a. Rawkode, does a deep dive on the Equinix GO SDK. David explores how to leverage webhooks and APIs with the Equinix SDK to build pipelines for remediation, automation, and notifications. We'll demonstrate how to send GET requests, showing the requests made and their results. This approach allows for dynamic capacity checks based on environment variables, integrated seamlessly with your infrastructure. This was a brief yet insightful introduction to the Equinix SDK. Go ahead, experiment with the Equinix SDK, and share your creations with us. Until next time, have a great day!
Authorization Tech with Jimmy Zelinskie, AuthZed
In this video, Chris Privitere from Equinix interviews Jimmy Zelinsky, CPO at AuthZed. AuthZed is the company behind SpiceDB, an open-source graph database optimized for authorization. Jimmy explains that authentication and authorization are the two main steps in accessing an application. Authentication verifies the identity of the user, while authorization checks if the user has the necessary access to perform certain actions. SpiceDB uses relationships between objects to model authorization, allowing users to define access based on relationships. Jimmy mentions that Google implemented similar concepts for Google Plus using a system called Zanzibar. AuthZed implemented SpiceDB based on the concepts from Google's Zanzibar, providing the same capabilities to other companies. They also recently launched a Kubernetes API proxy which allows users to secure the Kubernetes API with SpiceDB. Additionally, AuthZed offers a product called Materialize, which provides a materialized view of the graph and streams changes to other components in real-time. Jimmy suggests visiting the AuthZed website, blog, and Discord community for more information on their products.
Redesigned Developer Settings | Developer Platform
We have recently launched a for accessing your developer settings such as App Management and EMG subscriptions. With the improved UI, you can: Access your developer settings via Equinix portal and discover our product and services using a single unified login. Easily and efficiently manage your Equinix apps and subscriptions (including the ability to search, filter and sort) When logging in, you will be redirected to Equinix Customer Portal where you can sign in using your email login credentials. To access the app dashboard or EMG subscription, use the left navigation and select Developer Settings. There is no impact to existing apps and subscriptions and your integration will continue to work.Equinix Internet Access API docs - May 2023 updates
Equinix Internet Access 2023.3 release is mostly about ordering internet access service instance using a Fabric port, but it also introduces new endpoints for searching and viewing your EIA service instances. For more information, see Equinix Internet Access - 2023.3 Release Notes.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.0
