Detect & correct Compute node group without autoscaling

Overview

Compute node groups can be quite costly to retain, it is also likely that after a certain point in time they're no longer required and should be cleaned up to prevent further costs.

This query trigger detects compute node groups that have autoscaling disabled and then either sends a notification or attempts to perform a predefined corrective action.

Getting Started

By default, this trigger is disabled, however it can be configured by setting the below variables

compute_node_groups_without_autoscaling_trigger_enabled should be set to true as the default is false.
compute_node_groups_without_autoscaling_trigger_schedule should be set to your desired running schedule
compute_node_groups_without_autoscaling_default_action should be set to your desired action (i.e. "notify" for notifications or "enable_autoscaling_policy" to enable autoscaling policy).

Then starting the server:

flowpipe server

or if you've set the variables in a .fpvars file:

flowpipe server --var-file=/path/to/your.fpvars

Pipeline

Correct Compute node groups without autoscaling

Query

select
  concat(name, ' [', zone, '/', project, ']') as title,
  name,
  zone,
  _ctx ->> 'connection_name' as cred,
  project
from
  gcp_compute_node_group
where
  autoscaling_policy_mode <> 'ON';

Schedule

15m