Skip to main content

Overview

Locations show the available geographical locations for each of the following cloud providers:
  • Amazon Web Services (AWS)
  • Google Cloud Platform (GCP)
  • Microsoft Azure
  • Oracle Cloud Infrastructure (OCI)
Locations are scoped to an org, and an org administrator enables or disables the ones a GVC may select. A new org is seeded with a working subset of the built-in catalog, and every location present in an org starts enabled. Disabling a location removes the workloads running in it; enabling one provisions every workload whose GVC selects it.
If a company is restricted for legal or compliance reasons to only use certain cloud providers, disabling those providers will ensure that workloads will not be deployed to those providers.

Locations

Control Plane can enable any cloud provider location. If a location is not shown, email support@controlplane.com with the provider and location and it will be provisioned.

BYOK Locations

CPLN BYOK adds locations backed by Kubernetes clusters you run, in your own cloud accounts or on bare metal servers and on-premises VMs. A BYOK location has the provider byok, and you create it, install it into each cluster that serves it, and delete it yourself. Deploy a Workload to Your Own Hardware creates one and connects either an existing cluster or Linux servers to it.

Built-in Tags

Each location has the following built-in tags:
  • cpln/city=VALUE
  • cpln/state=VALUE
  • cpln/country=VALUE
  • cpln/continent=VALUE
These are set from the location’s geographic coordinates, so a GVC can select locations with a query on them instead of naming each one.

Egress IP Addresses

Outbound (egress) traffic from a workload leaves through the NAT gateway IPs of the location it runs in. Each location publishes these addresses in its ipRanges field. A location usually has a small set of them, and every workload in that location shares them. These IPs are very stable. They change rarely, and Control Plane aims to give advance notice when they do.
An IP Set does not change a workload’s egress IP. IP Sets apply to inbound traffic only.

View a Location’s Egress IPs

Navigate to the Locations list page from the main navigation bar. Select a location to view the IP ranges listed on the Info page.

Allowlist Outbound Traffic

When an external service accepts traffic only from known IPs, use one of these approaches, from simplest to most involved:
  1. Allowlist the location’s egress IPs. This works for most cases.
  2. Run the GVC in a single location. The external service then only needs that one location’s IPs. See GVC locations.
  3. Automate the allowlist. Read the location’s ipRanges from the API on a schedule and update the external service’s allowlist if they change.
  4. Use a location backed by your own cluster. For a single fixed egress IP, run workloads on a CPLN BYOK or Managed Kubernetes cluster in your own cloud account and assign a static IP to that cluster’s NAT gateway. This adds the cost of running a dedicated cluster, so prefer the location’s published IPs when they meet your needs.

Permissions

The permissions below are used to define policies together with one or more of the four principal types:

Access Report

Displays the permissions granted to principals for the location. See Access Report for what each entry shows, how to open it from the Console, CLI, or API, and how groups, query targets, and implied permissions appear in it.

CLI

To view the CLI documentation for locations, see the Location CLI reference.