Create a BYOC Cluster on GCP

To create a Redpanda cluster in your virtual private cloud (VPC), log in to Redpanda Cloud. Enter your organization name, and click Continue.

With standard BYOC clusters, Redpanda manages security policies and resources for your VPC, including subnetworks, service accounts, IAM roles, firewall rules, and storage buckets. For the most security, you can manage these resources yourself with a customer-managed VPC on GCP.

Create a BYOC cluster

  1. On the Home page, select your namespace, or create a new one.

    Namespaces help you organize clusters and resources. For example, you can create namespaces for different teams or projects. A default namespace is created with every organization. When an organization has more than one namespace, you can select the namespace where you want to create a new cluster.

  2. Click Create cluster, then click Create BYOC cluster.

    Enter a cluster name, and select the provider (GCP), region, availability zone type (single AZ or multi AZ) and zones, tier, and Redpanda version.

    • If you plan to create a private network in your own VPC, select the region where your VPC is located.

    • Three availability zones provide two backups in case one availability zone goes down.

    Optionally, click Advanced settings to specify up to five key-value custom labels. After the cluster is created, the labels are applied to all GCP resources associated with this cluster. For more information, see the GCP documentation.

  3. Click Next.

  4. On the Network page, enter the connection type: either Public or Private. For BYOC clusters, Private is best-practice.

    • Your network name is used in the Redpanda UI to identify this network.

    • For a CIDR range, choose one that does not overlap with your existing VPCs or your Redpanda network.

  5. Click Next.

  6. On the Deploy page, you need to prepare your environment, then log in to Redpanda Cloud and deploy the agent.

Note that rpk configures the permissions required by the agent to provision and actively maintain the cluster. For details about these permissions, see GCP IAM permissions.