Mantenha tudo organizado com as coleções
Salve e categorize o conteúdo com base nas suas preferências.
Nesta página, descrevemos como criar ou atualizar recursos de grupo de anexos no Google Distributed Cloud (GDC) isolado.
Um grupo de anexos representa uma coleção de anexos da VLAN que
compartilham o acesso a um conjunto de organizações. Um recurso AttachmentGroup lista
as organizações autorizadas a usar o roteamento e encaminhamento virtual (VRF) no recurso
InterconnectAttachment.
Os grupos de anexos são um recurso necessário para configurar uma conexão segura isolada com alta largura de banda e baixa latência.
Esta página é destinada a desenvolvedores do grupo de operadores de aplicativos que querem estabelecer conectividade com interconexões. Para mais informações, consulte Públicos-alvo para documentação isolada do GDC.
Antes de começar
Para criar ou atualizar um grupo de anexos, você precisa ter o seguinte:
IDENTIFIER: uma string de identificador exclusivo
para o grupo de anexos.
ORG_NAME: o nome da organização
do locatário a que todos os anexos da VLAN no grupo de anexos
podem se conectar. Precisa ser o nome da sua organização.
DOMAIN_TYPE: o domínio específico da
organização do locatário na entrada a que todos os anexos da VLAN podem
se conectar. Você precisa fornecer um dos seguintes valores válidos:
OrgAdmin: conecte-se à infraestrutura do plano de gerenciamento da organização.
OrgData: conecte-se à infraestrutura do plano de dados da organização.
OrgMixed: Use o tipo OrgMixed para se conectar à infraestrutura do plano de gerenciamento e do plano de dados da organização.
External: Use o tipo External se a organização não for uma organização da arquitetura Org v2.
[[["Fácil de entender","easyToUnderstand","thumb-up"],["Meu problema foi resolvido","solvedMyProblem","thumb-up"],["Outro","otherUp","thumb-up"]],[["Difícil de entender","hardToUnderstand","thumb-down"],["Informações incorretas ou exemplo de código","incorrectInformationOrSampleCode","thumb-down"],["Não contém as informações/amostras de que eu preciso","missingTheInformationSamplesINeed","thumb-down"],["Problema na tradução","translationIssue","thumb-down"],["Outro","otherDown","thumb-down"]],["Última atualização 2025-09-04 UTC."],[[["\u003cp\u003eThis guide outlines the process for creating or updating an attachment group in Google Distributed Cloud (GDC) air-gapped environments.\u003c/p\u003e\n"],["\u003cp\u003eAn attachment group is a collection of VLAN attachments that share access to specified organizations, and it lists organizations permitted to use virtual routing and forwarding (VRF) on the \u003ccode\u003eInterconnectAttachment\u003c/code\u003e resource.\u003c/p\u003e\n"],["\u003cp\u003eCreating or updating an attachment group involves defining its configuration in a YAML file named \u003ccode\u003eattachmentgroup.yaml\u003c/code\u003e, including a unique identifier, the tenant organization name, and the domain type.\u003c/p\u003e\n"],["\u003cp\u003eYou can apply the configuration using \u003ccode\u003ekubectl\u003c/code\u003e and verify the successful creation of the attachment group by confirming that the \u003ccode\u003eReady\u003c/code\u003e column displays \u003ccode\u003eTrue\u003c/code\u003e.\u003c/p\u003e\n"]]],[],null,["# Create an attachment group\n\nThis page describes how to create or update attachment group resources in Google Distributed Cloud (GDC) air-gapped.\n\nAn attachment group represents a collection of VLAN attachments that\nshare access to a set of organizations. An `AttachmentGroup` resource lists\nthe organizations allowed to use virtual routing and forwarding (VRF) on the\n`InterconnectAttachment` resource.\n\nAttachment groups are a required resource in setting up a secure air-gapped connection with high bandwidth and low latency.\n\nThis page is for developers within the application operator group who are looking to establish connectivity with interconnects. For more information, see [Audiences for GDC air-gapped documentation](/distributed-cloud/hosted/docs/latest/gdch/resources/audiences).\n\nBefore you begin\n----------------\n\nTo create or update an attachment group, you must have the following:\n\n- The necessary identity and access roles. For more information, see [Prepare predefined roles and permissions](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/interconnects/interconnect-overview#prepare-roles).\n\nCreate or update an attachment group\n------------------------------------\n\nTo create or update an attachment group, follow these steps:\n\n1. Create a YAML file named `attachmentgroup.yaml`.\n2. Add the following content to the file:\n\n apiVersion: system.private.gdc.goog/v1alpha1\n kind: AttachmentGroup\n metadata:\n name: attachment-group-\u003cvar translate=\"no\"\u003eIDENTIFIER\u003c/var\u003e\n namespace: gpc-system\n spec:\n identifier: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eIDENTIFIER\u003c/span\u003e\u003c/var\u003e\n entities:\n - orgName: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eORG_NAME\u003c/span\u003e\u003c/var\u003e\n domainType: \u003cvar translate=\"no\"\u003e\u003cspan class=\"devsite-syntax-l devsite-syntax-l-Scalar devsite-syntax-l-Scalar-Plain\"\u003eDOMAIN_TYPE\u003c/span\u003e\u003c/var\u003e\n\n3. Replace the following:\n\n - \u003cvar translate=\"no\"\u003eIDENTIFIER\u003c/var\u003e: a unique identifier string for the attachment group.\n - \u003cvar translate=\"no\"\u003eORG_NAME\u003c/var\u003e: the name of the tenant organization that all VLAN attachments in the attachment group can connect to. This must be your organization's name.\n - \u003cvar translate=\"no\"\u003eDOMAIN_TYPE\u003c/var\u003e: the specific domain of the\n tenant organization in the entry that all VLAN attachments can\n connect to. You must provide one of the following valid values:\n\n - `OrgAdmin`: Connect to the Org Management-plane infrastructure.\n - `OrgData`: Connect to the Org Data-plane infrastructure.\n - `OrgMixed:` Use the `OrgMixed` type to connect to both the Org Management-plane and Org Data-plane infrastructure.\n - `External:` Use the `External` type if the organization is not an Org v2 Architecture organization.\n4. Create the attachment group:\n\n kubectl apply -f attachmentgroup.yaml -n gpc-system\n --kubeconfig=\u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e\n\n Replace \u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e with the path to the\n kubeconfig file for the Management API server.\n5. Check that the creation of attachment group is successful:\n\n kubectl get attachmentgroup -n gpc-system\n --kubeconfig=\u003cvar translate=\"no\"\u003eMANAGEMENT_API_SERVER\u003c/var\u003e\n\n The output returns the attachment group and shows `True` in the `Ready`\n column: \n\n NAME IDENTIFIER READY\n attachment-group-mixed mixed True\n\nWhat's next\n-----------\n\n- [Create a VLAN attachment](/distributed-cloud/hosted/docs/latest/gdch/platform/pa-user/interconnects/create-vlan-attachment)"]]
