apis
54 TopicsCluster-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 of previous 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 the Community Slack and Community 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 latest cloud-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.05.3KViews3likes1CommentWhat's the difference between Playground, Sandbox, and Production?
You might be deploying on Network Edge today to run through Charles_Randall's tutorial. While reading up on Network Edge at Developer Platform, then perhaps you're thinking "what's the difference between Playground, Sandbox, and Production?". In short: Playground is a test environment to test Equinix APIs, using static data without integrating within the actual API. Sandbox is a mock test environment to test Equinix APIs, using synthetic data (not production data) to integrate with Equinix APIs before moving to Production. Production is the live environment.4.4KViews2likes0CommentsBilling v2 API deprecation?
Hello, today I noticed that on the API documentation overview page it says that the Billing_v2 API is Deprecated. I can't find any further information on that and also noticed that, in contrast to the WorkVists_v1 API which is marked in the same way, no deprecation information can be found on the actual documentation page. Would you be able to provide some more information on the deprecation or links to where I can find it? I'm especially interested in whether this API is actually going to be disabled in the future and if there's any alternative to obtain invoice information programmatically and machine-readable. Thanks, JonasSolved520Views1like3CommentsNot able to use Equinix API, giving error - error:0A000438:SSL routines::tlsv1 alert internal error
when I am trying below command from my server curl -v https://api.equinix.com its giving below error error:0A000438:SSL routines::tlsv1 alert internal error It was working fine earlier. I am using below APIs for validating Azure Key https://api.equinix.com/fabric/v4/connections/validate But now even authentication API is also not working1.4KViews1like2CommentsAPI service accounts for Fabric API?
Currently I'm using the API token associated with my personal login to Equinix for the Fabric API. What's the best way to make an API token for a service sharable by a group of people at my company? Should I just make an Equinix login like first name Cloud last name Fabric, and then make an API token from that, or is there another way?Solved4.8KViews1like3CommentsCreate Virtual Devices Using Equinix APIs
You can create Virtual Devices using Equinix APIs. Many vendors, including Cisco, Fortinet, Palo Alto Networks, and others, offer firewalls and routers on our platform. Check out our use cases to understand the required steps and the set of APIs you need to create Clusters, SD-WANs, and other Self-Configured devices: https://developer.equinix.com/dev-docs/ne/getting-started/launch-cluster-device https://developer.equinix.com/dev-docs/ne/getting-started/launch-sdwan-device https://developer.equinix.com/dev-docs/ne/getting-started/launch-self-configured-device You could take advantage of the Postman collection listed on the above pages to get the payload to create any device type.3.8KViews1like1Comment