Cluster settings

Review or edit the settings of the onboarded cluster

Cluster Settings contains a variety of configurable parameters, including:

• General cluster settings

• Various customizations

• Cluster labels

• Status of the Agent connecting the cluster to PerfectScale

To navigate to the Custer Settings , go to the Overview tab and find the needed cluster from the list of onboarded clusters. Hover over the cluster and click on the Gear button.

Cluster settings

General Settings

General cluster settings

1. Cluster Name - (editable field) displays the name of the cluster.

2. Disconnect Cluster - click on the button to disconnect the cluster from PerfectScale.

3. Optimization Policy - specifies how resources should be allocated to achieve the desired level of resiliency. This allows setting policies to support the individual needs of your workloads. Keep the default or select one of the following values:

   • MaxSavings - maximum cost savings, the best for non-production environments

   • Balanced (default) - optimally balances cost and resiliency

   • ExtraHeadroom - the best fit for latency-sensitive environments

   • MaxHeadroom - keeps the environment above the highest spikes

   Discover more about customizing the Optimization policy here.

4. Region - (autodetected editable field) displays the region where the cluster is running.

5. Cloud Provider - (autodetected non-editable field) displays the cloud provider name.

6. Initialization Date - (non-editable field) displays the date when the cluster was added.

Click Save Changes button to save the changes or Cancel & Close to discard them.

Customizations

PerfectScale offers a range of customizable features designed to empower you in building your own optimized K8s ecosystem. These enhancements boost observability throughout your environment while streamlining processes like alerting, ticketing, and pricing management.

Explore the available customizations here.

Cluster labels

PerfectScale allows you to leverage your cluster labels, enabling you to organize and manage your Kubernetes clusters in the usual way. This capability is particularly helpful when managing large-scale Kubernetes environments with numerous clusters. By defining and applying cluster labels, you can streamline navigation and filtering across PerfectScale dashboards, ensuring quick access to the data you need.

Cluster labels

How to add a label

There are two seamless approaches to add cluster labels:

• From the cluster settings

• From the global settings

Add cluster labels from cluster settings

1. In the cluster list, click the gear icon next to the cluster name to open Cluster Settings.

2. Go to the Labels tab.

3. Click + New Label.

4. Enter the Label Key and Label Value.

The label key must be unique per cluster. If you attempt to add a label using a key that already exists on that cluster, the label will not be applied.

Both the Key and the Value are limited to a maximum of 225 characters. Only alphanumeric characters and the following special symbols are allowed: . - _ /.

1. Click Save.

Add cluster label - cluster settings

Add cluster labels from global settings

1. Navigate to Global Settings in the bottom-left corner of the screen.

2. Open Cluster Labels.

3. Under the desired cluster, click + New Label.

4. Enter the Label Key and Label Value.

The label key must be unique per cluster. If you attempt to add a label using a key that already exists on that cluster, the label will not be applied.

Both the Key and the Value are limited to a maximum of 225 characters. Only alphanumeric characters and the following special symbols are allowed: . - _ /.

1. Click Save.

Add cluster label - global settings

How to edit/delete a label

You can seamlessly edit or delete labels. Simply hover over the label in either the cluster settings or the global settings, and select the desired action.

Label actions

Agent

PerfectScale delivers its services through agents like the PSC Exporter and PSC AutoScaler. To continuously analyze your environment, provide recommendations, and execute automation on your clusters, it's essential to have the relevant agent installed.

PerfectScale Agent

If you don't see a green (upgrade available) or orange (upgrade required) indicator, it means the agent is up to date and no action is needed.

Easily check the current version of the Agent or delve into the Release Notes. Clicking the Release Notes button takes you to GitHub, where you can explore comprehensive release details, including changes and assets.

In order to ensure you receive superior service and benefit from the latest features, an update of the agent components might be needed. In that case, the relevant indicator will be raised to inform you whether the upgrade is available or required, along with further instructions provided.

Upgrade Available

Upgrade Available indicates that a new version is ready for installation, while PerfectScale continues data processing with the current version.

Click the Upgrade Available indicator to explore the details. To upgrade the agent, click the View Upgrade Instructions button and follow the provided guide.

Agent upgrade available

Use the --reset-then-reuse-values flag to reuse the values from the last deployment of a release, overriding only the parameters explicitly set in the command. This flag retains existing values and changes only specific parameters, ensuring all other values remain the same as in the previous deployment. NOTE: -- reset-then-reuse-values is only available in Helm 3.14 or newer versions.

If you are using the older Helm version, turn the Helm 3.14+ toggle off and upgrade the Agent with the provided Helm.

Upgrade Required

Upgrade Required indicates that the current version is incompatible, and an upgrade is required to continue data processing by PerfectScale.

Click the Upgrade Required indicator to explore the details. To upgrade the agent, click the View Upgrade Instructions button and follow the provided guide.

Agent upgrade required

Use the -- reset-then-reuse-values flag to reuse the values from the last deployment of a release, overriding only the parameters explicitly set in the command. This flag retains existing values and changes only specific parameters, ensuring all other values remain the same as in the previous deployment. NOTE: -- reset-then-reuse-values is only available in Helm 3.14 or newer versions.

If you are using an older Helm version, turn the Helm 3.14+ toggle off and upgrade the Agent with the provided Helm command.

Specifying an optimization policy or returning to the default

If you set an optimization policy or custom time window using helm upgrade, you won’t be able to change these settings in the UI until you revert them to the defaults.

When upgrading the Agent, you can seamlessly specify an optimization policy and set a custom time window.

To specify an optimization policy and/or a custom time window when installing the Agent, use the following command:

helm upgrade --install -n some-release-name --create-namespace some-namespace \
  --set secret.create=true \
  --set secret.clientId=CLIENT_ID \
  --set secret.clientSecret=CLIENT_SECRET \
  --set settings.clusterName=CLUSTER_NAME \
  --set settings.clusterOptimizationPolicy="MaxSavings" \ # specify a desired optimization policy
  --set settings.optimizationPolicyTimeWindow="21d" \ # set a desired custom time window
  perfectscale/exporter

To revert to the default optimization policy and time window, upgrade the Agent using the following command:

helm upgrade --install -n some-release-name --create-namespace some-namespace \
  --set secret.create=true \
  --set secret.clientId=CLIENT_ID \
  --set secret.clientSecret=CLIENT_SECRET \
  --set settings.clusterName=CLUSTER_NAME \
  perfectscale/exporter

To revert to the default optimization policy and time window, do not specify clusterOptimizationPolicy and optimizationPolicyTimeWindow.

Delete a cluster

The endpoint removes the cluster instance from PerfectScale.

There may be situations where you need to remove a cluster from PerfectScale. You can seamlessly delete a cluster using the Public API. Learn more here.