Skip to main content

​
Overview

A Global Virtual Cloud (GVC) defines a set of cloud providers and their locations. When creating a GVC you are in essence building an uber-cloud that is comprised of the specified locations. Workloads are deployed to the GVC which are then served from all the locations specified. Each org can have multiple GVCs, each with its own unique set of locations. A domain name owned at the org level can be assigned to a GVC for routing. Each domain is associated with exactly one GVC at a time. Callers can reach workloads using the assigned domain name.

​
Benefits

  • GVCs enable your workload to be deployed with ease to multiple cloud providers and locations
    • You choose the provider (AWS, Azure, and GCP) and their different locations
    • Select locations that are close to your end-users
    • Select the locations that fulfill the requirements of your workloads
    • Ensure maximum availability if a cloud provider has an occasional outage
  • You get granular controls to define the scaling characteristics of 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 that are assigned to a GVC and used by workloads when authentication is required for pulling 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.
Multiple pull secrets can be assigned to a GVC. A workload’s container will use the appropriate secret when pulling the image from a private registry. If there are multiple secrets, the container will cycle through each one. If authentication fails, the deployment will not be 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 DNS geo-routing based on latency. For more complex 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.