Control types for @turbot/azure-aks

• Azure > AKS > Managed Cluster > Active
• Azure > AKS > Managed Cluster > Approved
• Azure > AKS > Managed Cluster > CMDB
• Azure > AKS > Managed Cluster > Discovery
• Azure > AKS > Managed Cluster > Tags

Azure > AKS > Managed Cluster > Active

Take an action when an Azure AKS managed cluster is not active based on the
Azure > AKS > Managed Cluster > Active > * policies.

The Active control determines whether the resource is in active use, and if not, has
the ability to delete / cleanup the resource. When running an automated compliance
environment, it's common to end up with a wide range of alarms that are difficult
and time consuming to clear. The Active control brings automated, well-defined
control to this process.

The Active control checks the status of all defined Active policies for the
resource (Azure > AKS > Managed Cluster > Active > *),
raises an alarm, and takes the defined enforcement action. Each Active
sub-policy can calculate a status of active, inactive or skipped. Generally,
if the resource appears to be Active for any reason it will be considered Active.

Note: In contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

Azure > AKS > Managed Cluster > Approved

Take an action when an Azure AKS managed cluster is not approved based on Azure > AKS > Managed Cluster > Approved > * policies.

The Approved control checks the status of the defined Approved sub-policies for the resource. If the resource is not approved according to any of these policies, this control raises an alarm and takes the defined enforcement action.

For any enforcement actions that specify if new, e.g., Enforce: Delete unapproved if new, this control will only take the enforcement actions for resources created within the last 60 minutes.

See Approved for more information.

Azure > AKS > Managed Cluster > CMDB

Record and synchronize details for the Azure AKS managed cluster into the CMDB.

The CMDB control is
responsible for populating and updating all the attributes for that
resource type in the Guardrails CMDB.

Note: If CMDB is set to Skip for a resource, then it will not be added
to the CMDB, and no controls that target it will run.

CMDB controls also use the Regions policy associated with the resource. If
region is not in Azure > AKS > Managed Cluster > Regions policy, the CMDB control will delete the
resource from the CMDB.

Azure > AKS > Managed Cluster > Discovery

Discover all Azure AKS managed cluster resources and add them to the CMDB.

The Discovery control is responsible for finding resources of a specific type. It periodically searches for new resources and saves them to the CMDB. Once discovered, resources are then responsible for tracking changes to themselves through the CMDB control.

Note: Discovery and CMDB controls also use the Regions policy associated with the resource. If the region is not in Azure > AKS > Managed Cluster > Regions policy, the CMDB control will delete the resource from the CMDB.

Azure > AKS > Managed Cluster > Tags

Take an action when an Azure AKS managed cluster tags is not updated based on the Azure > AKS > Managed Cluster > Tags > * policies.

If the resource is not updated with the tags defined in Azure > AKS > Managed Cluster > Tags > Template, this control raises an alarm and takes the defined enforcement action.

See Tags for more information.