[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["很难理解","hardToUnderstand","thumb-down"],["信息或示例代码不正确","incorrectInformationOrSampleCode","thumb-down"],["没有我需要的信息/示例","missingTheInformationSamplesINeed","thumb-down"],["翻译问题","translationIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-09-05。"],[[["\u003cp\u003eInterconnects establish a direct physical connection between your on-premises network and Google's network, ideal for high bandwidth, low latency, and secure connectivity needs.\u003c/p\u003e\n"],["\u003cp\u003eConfiguring an interconnect in Google Distributed Cloud (GDC) air-gapped requires coordination with your Infrastructure Operator (IO) to create resources in a specific order.\u003c/p\u003e\n"],["\u003cp\u003eThe interconnect creation process involves defining \u003ccode\u003eInterconnectLink\u003c/code\u003e, \u003ccode\u003eInterconnectGroup\u003c/code\u003e, \u003ccode\u003eAttachmentGroup\u003c/code\u003e, \u003ccode\u003eRoutePolicy\u003c/code\u003e, and \u003ccode\u003eInterconnectAttachment\u003c/code\u003e resources.\u003c/p\u003e\n"],["\u003cp\u003eTo manage interconnect resources, users must have the \u003ccode\u003einterconnect-admin\u003c/code\u003e cluster role, granted by the Organization IAM Admin.\u003c/p\u003e\n"],["\u003cp\u003eThe instructions for creating interconnects can also be used to update existing interconnect resources by modifying the YAML files and applying the changes using \u003ccode\u003ekubectl apply -f\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Overview\n\nThis page outlines the workflow for setting up a direct connection between your on-premises network and Google's network. It explains the steps involved in configuring an interconnect in Google Distributed Cloud (GDC) air-gapped.\n\nThis page is for developers within the application operator group who want to establish a secure air-gapped connection where they need to increase bandwidth with low latency. For more information, see [Audiences for GDC air-gapped documentation](/distributed-cloud/hosted/docs/latest/gdch/resources/audiences).\n\nYou must coordinate with the infrastructure operator group to successfully configure an interconnect. Submit a ticket in the GDC portal requesting an interconnect with your chosen specifications, such as 10 G of redundant connectivity.\n\nInterconnect creation process\n-----------------------------\n\nTo create an interconnect or VLAN attachment, you and the IO must create all of the following custom\nresources in the specified order:\n\n1. `InterconnectLink`: a representation of the physical cable that connects you to a GDC instance. The IO configures this resource.\n2. `InterconnectGroup`: a logical grouping of interconnect links that share a common purpose. The IO configures this resource.\n3. `AttachmentGroup`: a collection of VLAN attachments that share access to a set of organizations. You configure this resource.\n4. `RoutePolicy`: specifies what subnets are allowed to be advertised across the VLAN attachment. You must ask the IO to configure this resource.\n5. `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.\n\nInterconnection creation for a multi-zone universe\n--------------------------------------------------\n\nIf you are configuring interconnects for a multi-zone universe, you must follow the requirement for zonal symmetry. To access services and resources in a particular zone, you must create an interconnect that connects your network to that zone. In the case of a [multi-zone universe](/distributed-cloud/hosted/docs/latest/gdch/resources/multi-zone/mz-overview#deployment-hierarchy-overview), you must create an interconnect for each zone in that universe. One interconnect does not work across zones. For the multi-zone configuration, each interconnect must be identical to one another for each zone in the multi-zone universe.\n\nPrepare predefined roles and permissions\n----------------------------------------\n\nTo interact with interconnect resources, you must have access to the\nfollowing identity and access roles:\n\n- Ask your Organization IAM Admin to grant you the Interconnect Admin (`interconnect-admin`) cluster role. For more information, see [Predefined role descriptions](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/iam/role-descriptions).\n\nCreate or update interconnects\n------------------------------\n\nThe instructions in this section specify creation operations. However, you can\nalso use these instructions to update existing interconnect resources. Update\nthe YAML files and apply the updated file using the command `kubectl apply -f`.\n\nWhat's next\n-----------\n\n- [Create an attachment group](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/interconnects/create-attachment-group)"]]
