GDC air-gapped 提供两个级别的管理平面 API，用于创建和管理全局资源和可用区资源：全局 API 和可用区 API。
全局 API 和区域 API 都是在不同端点提供的 Kubernetes 声明性 API，GDC 资源在 API 服务器中表示为 Kubernetes 自定义资源。在每个组织中，可用区管理 API 服务器都会提供可用区 API，供管理员和开发者管理可用区资源；而全局管理 API 服务器则会提供全局 API，供管理员和开发者管理全局资源。
[[["易于理解","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-04。"],[[["\u003cp\u003eGoogle Distributed Cloud (GDC) air-gapped operates with both zonal and global resources, each managed independently by their respective API servers, providing a single endpoint for resource management.\u003c/p\u003e\n"],["\u003cp\u003eThere is always one global API server and one zonal API server for each zone, even in single-zone environments, ensuring resources are managed either within a specific zone or across multiple zones.\u003c/p\u003e\n"],["\u003cp\u003eResources are categorized as either zonal, operating within a single zone and vulnerable to zonal outages, or global, operating with redundancy across multiple zones for fault tolerance.\u003c/p\u003e\n"],["\u003cp\u003eThe GDC console and the gdcloud CLI, along with APIs and Terraform, provide tools to manage resources by targeting either the zonal or global API servers, allowing for flexible resource deployment and management.\u003c/p\u003e\n"],["\u003cp\u003eThe GDC console and gdcloud CLI offer zone-specific controls, like a zone scope picker and a \u003ccode\u003e--zone\u003c/code\u003e flag, respectively, enabling users to target and manage resources in designated zones.\u003c/p\u003e\n"]]],[],null,["# Global and zonal resources\n\nThis document explains the differences between global and zonal resources, and\nhow they operate in a multi-zone universe. Google Distributed Cloud (GDC) air-gapped\nprovides different deployment areas for your resources so you can implement high\navailability strategies for your workloads and services. You must understand the\nmulti-zone architecture and how resources span those zones to effectively plan\nfor highly available applications.\n\nThis document is for IT administrators within the platform administrator group\nwho are responsible for developing disaster recovery workflows, and application\ndevelopers within the application operator group who are responsible for\ndeveloping and maintaining applications in a GDC\nuniverse.\n\nFor more information, see\n[Audiences for GDC air-gapped documentation](/distributed-cloud/hosted/docs/latest/gdch/resources/audiences).\n\nResource types in GDC\n---------------------\n\nGDC air-gapped operates as a multi-zone universe. This\noperating model uses two resource types:\n\n- **Zonal resource** : Operates within a single zone independently, and is not managed outside the scope of that zone. A zonal outage can affect a zonal resource since the resource does not function outside the zone. You deploy a zonal resource to the zonal management API server, or more commonly referred to as the *management API server*.\n- **Global resource** : Operates with redundancy across multiple zones for fault tolerance, and is accessible by any resource in any zone. You deploy a global resource to the global management API server, or more commonly referred to as the *global API server*.\n\nZonal and global resources are managed differently by the\nGDC system with the use of distinct management API\nservers. An API server provides a single endpoint for creating, managing, and\ndeleting API resources with a strongly consistent storage backend.\nGDC provides [interfaces](#interfaces) so you can\neffectively manage your resources in the various API servers within your\nuniverse.\n\nThere is always only one global API server for your universe. Likewise, there is\na zonal management API server for each zone that you operate. Even if you\noperate in a single zone environment, there is one global API server and a zonal\nmanagement API server for the single zone.\n\nThis diagram illustrates a three zone GDC universe. Each\nzone has an independent zonal management API server, which manages the zonal\nresources that live within the scope of that zone. The universe also provides a\nglobal API server, which manages the global resources, such as projects, that\nspan all zones.\n\nYou must have an understanding of GDC's global resource\nmanagement architecture to appropriately\n[deploy your resources for high availability](/distributed-cloud/hosted/docs/latest/gdch/platform-application/pa-ao-operations/ha-apps/overview).\nWhile some resources can be deployed both globally or operate in a single zone\nindependently, there are others that are global or zonal only. Refer to the\nappropriate documentation of a resource type for more information.\n\nInterfaces for resource management\n----------------------------------\n\nGDC provides multiple surfaces that each provide\nmechanisms to appropriately deploy your zonal or global resource to a designated\nAPI server:\n\n- [**GDC console**](#console): A console interface that gives access to your resources across your universe.\n- [**gdcloud CLI**](#gdcloud): A dedicated CLI tool for GDC air-gapped, which gives zonal and global configurations and flags to manage all resource types.\n- [**Management APIs**](#management-apis): Management plane APIs that give you total control over fine-tuning your resource types zonally and globally.\n- [**Terraform**](#terraform): An infrastructure-as-code (IaC) tool that lets you provision and manage cloud infrastructure zonally and globally.\n\n| **Note:** The GDC console is based on the underlying GDC APIs. However, there might be some gaps in functionality between the GDC console and the API and the gdcloud CLI.\n\nYou can choose the surface to manage your resources based on your needs and\npreferences. For more information about how to use each surface to manage your\nresources in a multi-zone universe, see\n[Manage resources across zones](/distributed-cloud/hosted/docs/latest/gdch/resources/multi-zone/manage-mz-resources).\n\n### GDC console\n\nThe GDC console for a given organization is accessible from every zone\nwithin the same universe. Therefore, you can use the GDC console to\nmanage all global and zonal resources within an organization.\n\nThe GDC console provides several ways to view and manage your\nresources based on their deployment location:\n\n- **Navigate using a fully qualified domain name (FQDN):** Use the global FQDN to automatically resolve to the most appropriate zonal console endpoint. If the global FQDN fails to resolve in a disruption, you can use the zonal FQDN to navigate to a specific console endpoint in a target zone.\n- **Manage zonal resource creation:** Use the zone picker on select resource creation pages to determine where to create a zonal resource. The zone picker is not visible when you create a global resource.\n- **View existing resources across zones:** View zonal resources by zone in the GDC console. You can use the zone picker to select from which zone to view the list of resources.\n- **Be aware of zonal connectivity status:** Monitor your zone's connectivity status by reviewing notifications in the GDC console. Notifications could alert you of a zonal outage that might block you from modifying resources in that zone.\n\nFor more information on how to use the GDC console to create and\nmanage your resources, see the corresponding resource documentation.\n\n### gdcloud CLI\n\nThe gdcloud CLI provides the following ways to interact with the\nzonal or global API server to manage your resources:\n\n- **Configure a zonal or global console URL**: Sign in to the zonal or global console URL using the CLI.\n- **Define a zonal command flag**: Use a zonal CLI flag for specific zone actions.\n\nThe global URL is what is configured by default when\n[initializing the gdcloud CLI](/distributed-cloud/hosted/docs/latest/gdch/resources/gdcloud-install#init-default-config).\nYou can [update your gdcloud CLI configuration](/distributed-cloud/hosted/docs/latest/gdch/resources/gdcloud-manage-configurations)\nto set zonal URLs and sign in to them to complete zone-specific tasks.\n\nLikewise, the gdcloud CLI offers a `--zone` flag that you can set for\nmany resource management tasks across command groups. When signed in to the\nglobal URL configuration, your CLI actions on global resources are applied to\nall zones for which they are in scope.\n\nFor more information on the gdcloud CLI, see the\n[gdcloud CLI overview](/distributed-cloud/hosted/docs/latest/gdch/resources/gdcloud-overview).\n\n### Management APIs\n\nGDC air-gapped offers two levels of management plane\nAPIs to create and manage both global and zonal resources: global APIs and zonal\nAPIs.\n\nBoth global and zonal APIs are Kubernetes declarative APIs served at different\nendpoints, and GDC resources are represented as\nKubernetes custom resources in the API servers. In every organization, a zonal\nmanagement API server provides the zonal API for administrators and developers\nto manage zonal resources, and a global management API server provides the\nglobal API to manage global resources.\n\nFor more information on APIs in GDC, see the\n[APIs overview](/distributed-cloud/hosted/docs/latest/gdch/apis/apis-overview).\n\n### Terraform\n\nGDC air-gapped offers a seamless way to deploy and\nmanage all your resource types using\n[Terraform](https://developer.hashicorp.com/terraform). You use the\n[Kubernetes Provider](https://registry.terraform.io/providers/hashicorp/kubernetes/latest/docs)\nplugin to call the available zonal and global management APIs using industry\nstandard Terraform lifecycle management.\n\nFor more information, see the\n[Terraform overview](/distributed-cloud/hosted/docs/latest/gdch/resources/terraform).\n\nWhat's next\n-----------\n\n- Read the [Zones in GDC air-gapped](/distributed-cloud/hosted/docs/latest/gdch/resources/multi-zone/mz-overview) to learn more about the composition of a GDC universe.\n- Explore the [High availability guide](/distributed-cloud/hosted/docs/latest/gdch/platform-application/pa-ao-operations/ha-apps/overview) to ensure your application is resilient to local zone failures.\n- Visit the [gdcloud CLI reference documentation](/distributed-cloud/hosted/docs/latest/gdch/resources/gdcloud-reference/gdcloud) for a comprehensive list of gdcloud CLI commands that are available.\n- Visit the [API reference documentation](/distributed-cloud/hosted/docs/latest/gdch/apis/service-api-overview) for a comprehensive list of zonal and global APIs that are available.\n- To configure Terraform, see the [Terraform documentation](/distributed-cloud/hosted/docs/latest/gdch/resources/configure-terraform)."]]
