Skip to content

Latest commit

 

History

History
30 lines (21 loc) · 2.01 KB

context-switcher.md

File metadata and controls

30 lines (21 loc) · 2.01 KB

Contexts

Kubecost supports the ability to monitor multiple contexts of clusters. A context refers to either a single monitored cluster, or a set of clusters that leverage durable storage.

Add from frontend

When adding a context directly from the frontend, Kubecost adds it locally for your browser. To make this context accessible to other users in your organization, follow the steps to add at install-time below.

  1. Install Kubecost on the additional cluster you would like to view. The recommended Kubecost install path is available at kubecost.com/install.
  2. Expose port 9090 of the kubecost-cost-analyzer pod. This can be done with a Kubernetes Ingress (example) or LoadBalancer (example).
  3. Select Settings in the left navigation.
  4. Under Context Settings, select the bubble containing the name of your current context. The Contexts window opens.
  5. Select Add Cluster, then provide the accessible URL (with port included) for the target Kubecost installation, then select Add.

{% hint style="warning" %} By default, a LoadBalancer exposes endpoints to the wide internet. Be careful about following the authentication requirements of your organization and environment. {% endhint %}

In the Context Name text box, you can rename your current context. Remember to confirm your change by selecting Save at the bottom of the Settings page.

Add at install-time

After following Steps 1 and 2 above, provide a list of context names/endpoints under kubecostProductConfigs.clusters in your values.yaml during Helm install or upgrade. Here's an example values block:

 kubecostProductConfigs:
  clusters:
   - name: "Cluster A"
     address: http://cluster-a.kubecost.com:9090