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)
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 providerbyok, 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=VALUEcpln/state=VALUEcpln/country=VALUEcpln/continent=VALUE
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 itsipRanges 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
- Console UI
- CLI
- API
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:- Allowlist the location’s egress IPs. This works for most cases.
- Run the GVC in a single location. The external service then only needs that one location’s IPs. See GVC locations.
- Automate the allowlist. Read the location’s
ipRangesfrom the API on a schedule and update the external service’s allowlist if they change. - 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.