This page provides an overview for how to configure an interconnect in Google Distributed Cloud (GDC) air-gapped.
Interconnects allow you to establish a direct physical connection between your on-premises network and Google's network. This is useful for situations where you need high bandwidth, low latency, and secure connectivity.
You must coordinate with your Infrastructure Operator (IO) to successfully configure an interconnect. Submit a ticket in the GDC portal requesting an interconnect with your chosen specifications, such as 10G of redundant connectivity.
Interconnect creation process
To create an interconnect or VLAN attachment, you and the IO must create all of the following custom resources in the specified order:
InterconnectLink: a representation of the physical cable that connects you to a GDC instance. The IO configures this resource.InterconnectGroup: a logical grouping of interconnect links that share a common purpose. The IO configures this resource.AttachmentGroup: a collection of VLAN attachments that share access to a set of organizations. You configure this resource.RoutePolicy: specifies what subnets are allowed to be advertised across the VLAN attachment. You must ask the IO to configure this resource.InterconnectAttachment: the VLAN attachment. This resource links your network's VLAN to a GDC instance with BGP for routing, enabling private and controlled access. You configure this resource.
Prepare predefined roles and permissions
To interact with interconnect resources, you must have access to the following identity and access roles:
- Ask your Organization IAM Admin to grant you the Interconnect Admin
(
interconnect-admin) cluster role. For more information, see Predefined role descriptions.
Create or update interconnects
The instructions in this section specify creation operations. However, you can
also use these instructions to update existing interconnect resources. Update
the YAML files and apply the updated file using the command kubectl apply -f.