Cloud Infrastructure Made Easy: IaC Demo Day!
Hey everyone! We’re thrilled to be hosting our second Demo Day of 2024, this time all about Infracode! If you’re already an infrastructure expert slinging Terraform or just starting out, we’ve got experts from across the industry to share their experiences with you! We’ll have folks like Marino Wijay of Kong talking about Platform best practices for AI, Jared Watts talking about Crossplane, and Engin Diri to talk to us about Pulumi. We’ve even got two of our Equinix DevRel Engineers, Chris Privitere and Oscar Cobles to talk about Kubernetes Cluster API and using Terraform to interconnect Equinix Metal and your AWS cloud. See our Event Page for more information and/or join us live at the link below so you can post your questions for our speakers directly in the chat! Can’t wait to see you in the chat! P.S. -- if you can’t make it, or you’re getting this late, don’t panic! Our full session will be embedded belowCrayZeigh2 days agoEquinix Employee20Views2likes0CommentsWhat’s your most interesting on-call story?
In the interest of getting to know you all a bit better, we thought it would be fun to pose a Question of the Month. Each month we'll introduce a new topic and give you all the floor to share your stories, thoughts, and anecdotes. We look forward to hearing from you! This month's question is: What’s your most interesting on-call story? Whether it’s the time you got called to restore from backups after a power outage, or the time someone accidentally deleted the prod environment, we want to hear about your most interesting on-call stories.ChrisR4 days agoModerator10Views0likes0CommentsConnecting multiple clouds is hard – we make it easy. Join our beta!
If you're interested in trying out something new and helping us make improvements in the field of multicloud networking, we'd love to have you join our Public Beta Program. What do you gain from joining the beta? Help shape the future of cloud technology Gain direct access to product managers See how Equinix is solving multicloud networking complexity with simple, high-performant new solutions How do I join the Beta? It’s easy: fill out this request form!tvader10 days agoEquinix Employee29Views0likes0Comments60 seconds about IFConfig and IPConfig
What can you learn in 60 seconds? A lot, actually! We're now creating Youtube Shorts to teach you in bite-size snippets. Let me and stevemar know which topics you'd like us to cover! Here I talk about IPConfig and IFConfig, which dives into your computer's network - like VPNs, ethernet ports, and more! https://www.youtube.com/shorts/Xh5KqfH7WE8waribeiro2 months agoEquinix Employee65Views4likes2CommentsFabric APIv4, Connection to azure, Technical background vlanSTag in zSide
Hello, I'd like to configure a redundant connection to Azure using dot1q encapsulation. The documentation for migration from v3 to v4 states that we need to include "linkProtocol": { "type": "QINQ", "vlanSTag": 2002 }, in the zSide definition. That was not necessary in the v3 API. I'm not sure what the technical background for that value is. Specifically: Can we always use the same VLAN ID in connections to different Azure environments when using unique VLAN IDs on the aSide? Any help is appreciated.dirkf2 months agoLevel 1188Views1like2CommentsCrossplane - Metal Vlan description not updated in UI
When editing an existing Metal Vlan resource's spec to add a description, the string is applied to the managed resource but is not updated in the UI. If the description is included in the original Vlan resource spec during creation, the UI shows the description. apiVersion: metal.equinix.jet.crossplane.io/v1alpha1 kind: Vlan metadata: name: myvlan1 spec: forProvider: description: | Dummy native VLAN for purposes of enabling tagging on the trunk port. projectId: <uuid> metro: sv If the spec.forProvider.description is left out during the creation, then editing the resource and applying the change will not cause the description to show up in the UI. I'm not sure if this is expected or not.152Views0likes1CommentCrossplane - failure to delete port resource in Claim
I have created a Claim that includes a Device, Port, PortVlanAttachment and a Vlan. In order to create the Port I have to pass the Device Eth1 port UUID to the 'spec.forProvider.portId' of the Port Kind. This works and picks up the vlan info, but upon deleting the claim, the port is not deleted automatically as expected. The following event messages can be seen: Conflicting configuration arguments: "vlan_ids": conflicts with vxlan_ids Warning CannotObserveExternalResource 8s (x10 over 6m27s) managed/metal.equinix.jet.crossplane.io/v1alpha1, kind=port cannot run refresh: refresh failed: Conflicting configuration arguments: "vlan_ids": conflicts with vxlan_ids Conflicting configuration arguments: "vxlan_ids": conflicts with vlan_ids The spec of the object looks like this: Spec: Deletion Policy: Delete For Provider: Bonded: false Port Id: b561e487-fbb0-4a2c-98e7-22da331ed316 Vlan Ids: 73f648b5-9b6b-4076-a6ab-673aa45c7152 Vxlan Ids: 1000 Provider Config Ref: Name: default In order to resolve the issue I need to manually delete the resources finalizer.460Views2likes7CommentsCrossplane Metal provider - lifecycle.prevent_destroy error
After I spin up a Metal Device using the Crossplane Equinix provider, it comes up but in the events I see the following. I'm not sure if it is expected or a bug? Managed resource event message: Events: Type Reason Age From Message ---- ------ ---- ---- ------- Normal CreatedExternalResource 3m7s managed/metal.equinix.jet.crossplane.io/v1alpha1, kind=device Successfully requested creation of external resource Warning CannotObserveExternalResource 13s (x6 over 30s) managed/metal.equinix.jet.crossplane.io/v1alpha1, kind=device cannot run plan: plan failed: Instance cannot be destroyed: Resource equinix_metal_device.my-gateway-sv-4x2x4-4gfpq has lifecycle.prevent_destroy set, but the plan calls for this resource to be destroyed. To avoid this error and continue with the plan, either disable lifecycle.prevent_destroy or reduce the scope of the plan using the -target flag. Field in XRD for plan is: "plan: m3.small.x86" Environment: Crossplane v1.16 Equinix Provider: v0.6.1 K8s: Kind 1.27186Views1like1Comment
Forum Widgets
Popular Tags
- developer167 Topics
- Network Optimization149 Topics
- Fabric112 Topics
- Network Edge101 Topics
- security90 Topics
- Hybrid Infrastructure86 Topics
- data centers78 Topics
- global business72 Topics
- Colocation66 Topics
- Interconnection Services63 Topics