This page provides a high-level overview of the end-to-end journey of your
Google Distributed Cloud connected hardware, from the initial order to a
fully functional deployment on your premises.

The process is divided into three phases:

1. [Ordering](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/lifecycle-overview#ordering)
2. [Delivery and physical installation](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/lifecycle-overview#delivery)
3. [Bring-up and configuration](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/lifecycle-overview#bring-up)

## Ordering

In the ordering phase, you plan your deployment, define your requirements, and
place your order.

1. **Plan your configuration**: Work with your network administrator and
   Google representatives to determine your hardware and network
   requirements.

   - Plan your [space](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/requirements#space), [power](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/requirements#power), and [cooling](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/requirements#cooling) requirements.
   - Select and procure [certified hardware](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/requirements#hardware) based on your workload requirements.
   - Allocate necessary [IP address blocks](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/requirements#address-blocks) for machine management, Kubernetes nodes, and control plane virtual IP addresses (VIPs). Ensure that your IP address allocations are accurate. You cannot change these network configurations after the hardware is deployed.
2. **Validate connectivity** : Run the
   [network connectivity validation tool](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/requirements#validate-connectivity)
   on your local network to ensure that it meets all requirements for Domain Name System (DNS),
   Network Time Protocol (NTP), firewalls, and bandwidth.

3. **Place the order** : Use the
   [Google Cloud console](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/order#order-console)
   or the
   [GDC Hardware Management API](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/order#order-api)
   to submit your order in your target project. The order includes
   contact information, site details, hardware configuration, and network
   configuration. This information is provided to your Google-certified systems integrator (SI).

4. **Order review and contract** : A Google representative reviews your order,
   helps finalize the configuration, and works with you to sign the contract.
   After the order is accepted, the order state changes to `ACCEPTED`.

For more information, see
[Order hardware](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/order).

## Delivery and physical installation

In this phase, your Google-certified SI prepares and delivers the hardware and
installs it at your site.

1. **Hardware building** : Your Google-certified systems integrator builds and
   preconfigures the physical machines based on your order details. The order
   state transitions to `BUILDING`.

2. **Shipping** : The hardware is shipped to your site. The order state
   transitions to `SHIPPING`.

3. **On-site installation**:

   - A field technician from your SI arrives at your site.
   - The technician mounts the hardware in your rack or sets up the chassis.
   - Your network administrator works with the technician to connect the hardware to the power source and your local network, specifically the top-of-rack switches.
   - The technician activates the hardware. The order state transitions to `INSTALLING`. Ensure that your upstream Border Gateway Protocol (BGP) sessions and firewalls are configured before the technician starts activation, or the process will fail to complete.
4. **Verification**: After the hardware is installed and connected, the
   machines boot up and establish a secure VPN connection to Google Cloud.

   - Verify that the machines are registered and visible in the [**Edge Zones** menu in the Google Cloud console](https://console.cloud.google.com/distributed-cloud/edgezones/list).
   - Alternatively, use the [`gcloud edge-cloud container machines list`](https://docs.cloud.google.com/sdk/gcloud/reference/edge-cloud/container/machines/list) command to verify their status.

After verification is complete, the order state transitions to `COMPLETED`.

## Bring-up and configuration

In this phase, your cluster administrator configures the software environment,
creates clusters, and prepares the platform for workloads.

1. **Set up the Google Cloud project**:

   - [Enable the required Google Cloud APIs](https://docs.cloud.google.com/service-usage/docs/enable-disable), such as `edgecontainer.googleapis.com`, `edgenetwork.googleapis.com`, and `gkehub.googleapis.com`.
   - [Create Google service accounts](https://docs.cloud.google.com/iam/docs/service-accounts-create) for specific functions, such as image pulling and external secrets.
2. **Create a cluster** : Use the
   [`gcloud edge-cloud container clusters create`](https://docs.cloud.google.com/sdk/gcloud/reference/edge-cloud/container/clusters/create)
   command to provision a cluster on the deployed machines. It can take an hour
   or more to download and install the necessary software. You can
   [monitor the provisioning progress](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/clusters#monitor-provisioning).

3. **Configure networking**: Initialize the zone network and create VLAN
   subnetworks as required for your workloads. Distributed Cloud
   connected restricts direct access to the pod network. To enable
   communication with your local network, attach your workloads, especially
   virtual machines, to these L2 VLAN subnetworks.

4. **Configure access**:

   - Configure cluster access. Google recommends that you use [Connect gateway](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/clusters#gateway) as the primary access method to leverage Identity and Access Management. You can also configure [local credentials](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/clusters#credentials) for local administration.
   - [Configure Kubernetes Role-Based Access Control (RBAC)](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/users#kubernetes-rbac) to grant access to other administrators or developers.
5. **Configure storage** : To enable persistent storage,
   [apply your Symcloud Storage license](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/storage),
   which you obtain from Google Cloud Marketplace. You only apply the license.
   Google manages the underlying storage operator and storage pools.

   > [!WARNING]
   > **Warning:** Do not manually upgrade or modify the Google-managed operator for Symcloud Storage. Doing so renders Symcloud Storage inoperable.

The platform is now ready. You can deploy workloads, including containers
and virtual machines, to the cluster.

## Summary of responsibilities

| Action | Primary responsibility | Collaborators |
|---|---|---|
| **Planning and ordering** | Customer network administrator | Google sales and engineering |
| **Hardware provisioning** | Google-certified systems integrator | None |
| **Delivery and physical installation** | Field technician | Customer network administrator and site contact |
| **Google Cloud project configuration** | Customer cluster administrator | None |
| **Cluster creation and bring-up** | Customer cluster administrator | None |
| **Workload deployment** | Customer application owner | Customer cluster administrator |

## What's next

- [Installation requirements](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/requirements)
- [Order hardware](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/order)
- [Create and manage clusters](https://docs.cloud.google.com/distributed-cloud/connected/latest/docs/clusters)