GVC (Global Virtual Cloud)

Global Virtual Clouds (GVCs) group cloud providers and locations for workload deployment. Covers domain assignment, pull secrets, and multi-cloud isolation.

Overview

A Global Virtual Cloud (GVC) defines a set of cloud providers and deployment locations.

When creating a GVC effectively builds a unified multi-cloud environment that is comprised of the specified locations. Workloads are deployed to the GVC which are then served from all the configured locations.

Each org can have multiple GVCs, each with its own set of locations.

A domain name configured at the org level can be assigned to a GVC for routing. Each domain is associated with exactly one GVC at a time. Traffic is routed to workloads using the assigned domain name.

Benefits

• GVCs enable your workload to be deployed easily to multiple cloud providers and locations
  • Choose cloud providers such as (AWS, Azure, and GCP) along with their deployment locations
  • Select locations close to your end users
  • Select the locations that fulfill your workload requirements
  • Ensure maximum availability if a cloud provider experiences an outage
  • Configure granular scaling behavior for your workload

Domain Name

Domains are configured at the org level and routed to workloads via domain route configuration. The default domain name cpln.app is used for workload endpoints unless a custom domain is configured.

Pull Secrets

Pull secrets are secrets assigned to a GVC and used by workloads when authentication is required to pull an image from a private registry. Only the Docker, Amazon ECR, and GCP secret types are supported.

If the image was pushed to the Control Plane registry for the same org, no secret is required.

A GVC can have multiple pull secrets assigned. A workload’s container will use the appropriate secret when pulling images from a private registry. f multiple secrets are configured, the container attempts each secret in sequence.

If authentication fails, the deployment is not updated and the image pull will have an exponential backoff retry starting at 10 seconds until 5 minutes (e.g., 10 seconds, 20 seconds, 40 seconds, etc.).

Location Routing

By default, traffic is routed to the nearest healthy location using latency-based DNS geo-routing. For more advanced routing scenarios, you can configure location routing options on a per-GVC basis to control priority-based failover, adjust traffic distribution with latency offsets, and set latency thresholds for location availability.

Reference

Visit the GVC reference page for additional details.