Location

Cluster Administrators can optionally "inject" location metadata into their managed clusters during cluster import or provisioning.

For application owners, location can be an extremely useful and powerful way to "abstract" themselves from "individual clusters". i.e. treat Kubernetes clusters as "Cattle" instead of "Pets" with individual names. The location metadata can be transparently leveraged in placement/deployment policies.

---

Cluster "Location"

At time of import or provisioning of cluster (or anytime later), administrators can indicate "location" metadata. This metadata is made available for operational workflows related to clusters and workloads.

The controller provides a "default" list of locations (i.e. popular cities with significant end user populations) that the administrator can select for their clusters. If the default location list does not suit your needs, you can create “custom” locations and leverage it.

• Login into the WEb Console as an Org Admin
• On the bottom of the left panel, click on Cluster Locations.
• Click on New Location
• Provide a preferred name, country, city and Lat/Long

Going forward, the administrator can refer to the custom location vs. the actual city name. For example, the larger tech team may refer to their datacenter in the SF Bay Area as "West Coast Datacenter". They may not have a need to know the actual location of the datacenter.

---