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
Locations are scoped to an org and the org administrator can turn off/on the locations that are permitted when configuring a GVC. By default, all locations are enabled. If a location is disabled, any workloads within that location will be removed. Further, if a location is enabled, all workloads will be provisioned to that location.
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, please email [email protected] with the provider and location and it will be provisioned.

​
Custom Locations

CPLN Platform (BYOK) enables you to add new locations by registering your own Kubernetes clusters as locations in the Control Plane platform. For a guide on how to create new BYOK locations and further details, refer to the BYOK documentation.

​
Built-in Tags

Each location has the following built-in tags:
  • cpln/city=VALUE
  • cpln/country=VALUE
  • cpln/continent=VALUE

​
Public IPs

The list of public IPs for each cloud provider and region can be obtained from the following:
  • Console UI: The Locations page. Select the location to display the IP ranges.
  • CLI: Using the command cpln location get -o json will list the IPs in the ipRanges property. The output can also be formatted in YAML by using the flag -o yaml-slim.
  • API: Using the location endpoint. View the available endpoints here. The ipRanges property will contain the list of SIPs.
The list of IPs may be required by external services that restrict the IPs allowed to call them.The IPs may change when underlying infrastructure changes. Therefore, Control Plane recommends the automation of querying the location API for changes. In case of changes, the automation should re-configure external services’ allowed IP address list.

​
Permissions

The permissions below are used to define policies together with one or more of the four principal types:
PermissionDescriptionImplies
createCreate new locations
editModify existing locationsview
manageFull accesscreate, edit, manage, use, view
useUse this location for workload placementview
viewRead-only access

​
Access Report

Displays the permissions granted to principals for the location.

​
CLI

To view the CLI documentation for locations, click here.