We are introducing a significant enhancement to our customer experience for registering Kubernetes clusters in CloudHealth. The benefits of this feature are:
Reduce the number of steps required to register a new cluster using a Public Helm Chart
Clusters will be automatically registered if a CloudHealth Collector Agent is running on the cluster
Cluster information is visible automatically in Container Configuration and Perspective Builders
Ability to make CloudHealth Collector Agent deployment part of your CI/CD pipeline using Helm Chart
Select Setup > Containers > Clusters. From the Add Cluster dropdown, select Kubernetes (via Helm). For more information, please visit the Help Center documentation.

We are proud to introduce Google Cloud Platform Compute Engine resource actions that allow you to take Start/Stop actions for Compute Engine Instances. Especially powerful when combined with label filters, this feature can help users better manage and optimize their GCP environment with lights on/off policies. To configure Start/Stop policies, we require the permissions 'compute.instances.start' and 'compute.instances.stop'. To set up this start/stop action, go to:
Setup > Governance > Policies
Select New Policy > Standard Policy
Add the relevant details around Policy Name, Description
Select Resource Type to be Compute Instance
Add rules to monitor one or more conditions
Click Actions and select Start GCP Compute Instances or Stop GCP Compute Instances
Choose a Perspective Group to limit the scope of this action; Save Action
For more information, please visit the Help Center documentation.
