Policy types for @turbot/gcp-kubernetesengine

GCP > Kubernetes Engine > API Enabled

Check whether GCP Kubernetes Engine API is enabled.

API Enabled refers specifically to the API state of a service in a cloud project.
This control determines whether the API state is set as per desired level.

The GCP > Kubernetes Engine > API Enabled control compares
the API state against the API Enabled policies,
raises an alarm, and takes the defined enforcement action.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineApiEnabled
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Check: Enabled if Kubernetes Engine > Enabled",
"Enforce: Disabled",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine > Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Check: Enabled if Kubernetes Engine > Enabled",
"Enforce: Disabled",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine > Enabled"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Approved Regions [Default]

A list of GCP regions in which GCP Kubernetes Engine resources are approved for use.

The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.

This policy is the default value for all GCP Kubernetes Engine resources' Approved > Regions policies.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineApprovedRegionsDefault
Default Template Input
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp#/policy/types/approvedRegionsDefault\") {\n value\n }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- '{{ item }}'\n{% endfor %}"

GCP > Kubernetes Engine > CMDB

Record and synchronize details for GCP Kubernetes Engine kubernetes engine(s) into the CMDB.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineCmdb
Category
Valid Value
[
"Skip",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Enforce: Enabled"
}

GCP > Kubernetes Engine > Enabled

Enabled Kubernetes Engine.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineEnabled
Valid Value
[
"Enabled",
"Enabled: Metadata Only",
"Disabled"
]
Schema
{
"type": "string",
"enum": [
"Enabled",
"Enabled: Metadata Only",
"Disabled"
],
"example": [
"Enabled"
],
"default": "Disabled"
}

GCP > Kubernetes Engine > Labels Template [Default]

A template used to generate the keys and values for GCP Kubernetes Engine resources.

By default, all Kubernetes Engine resource Labels > Template policies will use this value.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineLabelsTemplate
Default Template Input
"{\n defaultLabels: policyValue(uri:\"tmod:@turbot/gcp#/policy/types/defaultLabelsTemplate\") {\n value\n }\n}\n"
Default Template
"{%- if $.defaultLabels.value | length == 0 %} [] {%- elif $.defaultLabels.value != undefined %}{{ $.defaultLabels.value | dump | safe }}{%- else %}{% for item in $.defaultLabels.value %}- {{ item }}{% endfor %}{% endif %}"

GCP > Kubernetes Engine > Permissions

Configure whether permissions policies are in effect for GCP Kubernetes Engine.
This setting does not affect Project level permissions (GCP/Admin, GCP/Owner, etc).

Note: The behavior of this policy depends on the value of GCP > Permissions.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEnginePermissions
Valid Value
[
"Enabled",
"Disabled",
"Enabled if GCP > Kubernetes Engine > Enabled"
]
Schema
{
"type": "string",
"enum": [
"Enabled",
"Disabled",
"Enabled if GCP > Kubernetes Engine > Enabled"
],
"example": [
"Enabled"
],
"default": "Enabled if GCP > Kubernetes Engine > Enabled"
}

GCP > Kubernetes Engine > Permissions > Levels

Define the permissions levels that can be used to grant access to Kubernetes Engine
an GCP project. Permissions levels defined will appear in the UI to assign access to Guardrails users.

Note: Some services do not use all permissions levels, and any permissions level that has
no permissions associated will not be created even if it is selected here.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEnginePermissionsLevels
Default Template Input
[
"{\n item: project {\n turbot{\n id\n }\n }\n}\n",
"{\n availableLevels: policyValues(filter:\"policyTypeLevel:self resourceId:{{ $.item.turbot.id }} policyTypeId:'tmod:@turbot/gcp-iam#/policy/types/permissionsLevelsDefault'\") {\n items {\n value\n }\n }\n}\n"
]
Default Template
"{% if $.availableLevels.items[0].value | length == 0 %} [] {% endif %}{% for item in $.availableLevels.items[0].value %}- {{ item }}\n{% endfor %}"
Schema
{
"type": "array",
"items": {
"type": "string",
"enum": [
"Metadata",
"ReadOnly",
"Operator",
"Admin",
"Owner"
]
}
}

GCP > Kubernetes Engine > Permissions > Levels > Modifiers

A map of GCP API to Guardrails Permission Level used to customize Guardrails' standard permissions.
You can add, remove or redefine the mapping of GCP API operations to Guardrails permissions levels here.

Note: Modifiers are cumulative - if you add a permission to the metadata level, it is also added
to readOnly, operator and admin. Modifier policies set here will “roll up” to the GCP level too - if
you add a permission to Admin, it will be granted to GCP/Storage/Admin and also GCP/Admin

<br />example:<br /> - &quot;storage.bucket.create&quot;: admin<br /> - &quot;sql.database.create&quot;: metadata<br />

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEnginePermissionsLevelsModifiers

GCP > Kubernetes Engine > Region Cluster > Active

Determine the action to take when an GCP Kubernetes Engine region cluster, based on the GCP > Kubernetes Engine > Region Cluster > Active > * policies.

The 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 (GCP > Kubernetes Engine > Region 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 the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

See Active for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterActive
Valid Value
[
"Skip",
"Check: Active",
"Enforce: Delete inactive with 1 day warning",
"Enforce: Delete inactive with 3 days warning",
"Enforce: Delete inactive with 7 days warning",
"Enforce: Delete inactive with 14 days warning",
"Enforce: Delete inactive with 30 days warning",
"Enforce: Delete inactive with 60 days warning",
"Enforce: Delete inactive with 90 days warning",
"Enforce: Delete inactive with 180 days warning",
"Enforce: Delete inactive with 365 days warning"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Active",
"Enforce: Delete inactive with 1 day warning",
"Enforce: Delete inactive with 3 days warning",
"Enforce: Delete inactive with 7 days warning",
"Enforce: Delete inactive with 14 days warning",
"Enforce: Delete inactive with 30 days warning",
"Enforce: Delete inactive with 60 days warning",
"Enforce: Delete inactive with 90 days warning",
"Enforce: Delete inactive with 180 days warning",
"Enforce: Delete inactive with 365 days warning"
],
"example": [
"Check: Active"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Active > Age

The age after which the GCP Kubernetes Engine region cluster
is no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.

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 (GCP > Kubernetes Engine > Region 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 the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterActiveAge
Valid Value
[
"Skip",
"Force inactive if age > 1 day",
"Force inactive if age > 3 days",
"Force inactive if age > 7 days",
"Force inactive if age > 14 days",
"Force inactive if age > 30 days",
"Force inactive if age > 60 days",
"Force inactive if age > 90 days",
"Force inactive if age > 180 days",
"Force inactive if age > 365 days"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Force inactive if age > 1 day",
"Force inactive if age > 3 days",
"Force inactive if age > 7 days",
"Force inactive if age > 14 days",
"Force inactive if age > 30 days",
"Force inactive if age > 60 days",
"Force inactive if age > 90 days",
"Force inactive if age > 180 days",
"Force inactive if age > 365 days"
],
"example": [
"Force inactive if age > 90 days"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Active > Last Modified

The number of days since the GCP Kubernetes Engine region cluster was last modified before it is considered
inactive.

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 (GCP > Kubernetes Engine > Region 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 the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterActiveLastModified
Valid Value
[
"Skip",
"Active if last modified <= 1 day",
"Active if last modified <= 3 days",
"Active if last modified <= 7 days",
"Active if last modified <= 14 days",
"Active if last modified <= 30 days",
"Active if last modified <= 60 days",
"Active if last modified <= 90 days",
"Active if last modified <= 180 days",
"Active if last modified <= 365 days",
"Force active if last modified <= 1 day",
"Force active if last modified <= 3 days",
"Force active if last modified <= 7 days",
"Force active if last modified <= 14 days",
"Force active if last modified <= 30 days",
"Force active if last modified <= 60 days",
"Force active if last modified <= 90 days",
"Force active if last modified <= 180 days",
"Force active if last modified <= 365 days"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Active if last modified <= 1 day",
"Active if last modified <= 3 days",
"Active if last modified <= 7 days",
"Active if last modified <= 14 days",
"Active if last modified <= 30 days",
"Active if last modified <= 60 days",
"Active if last modified <= 90 days",
"Active if last modified <= 180 days",
"Active if last modified <= 365 days",
"Force active if last modified <= 1 day",
"Force active if last modified <= 3 days",
"Force active if last modified <= 7 days",
"Force active if last modified <= 14 days",
"Force active if last modified <= 30 days",
"Force active if last modified <= 60 days",
"Force active if last modified <= 90 days",
"Force active if last modified <= 180 days",
"Force active if last modified <= 365 days"
],
"example": [
"Active if last modified <= 90 days"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Approved

Determine the action to take when a GCP Kubernetes Engine region cluster is not approved based on GCP > Kubernetes Engine > Region 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.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterApproved
Valid Value
[
"Skip",
"Check: Approved",
"Enforce: Delete unapproved if new"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Approved",
"Enforce: Delete unapproved if new"
],
"example": [
"Check: Approved"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Approved > Custom

Determine whether the GCP Kubernetes Engine region cluster is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine region cluster is not approved, it will be subject to the action specified in the GCP > Kubernetes Engine > Region Cluster > Approved policy.
See Approved for more information.

Note: The policy value must be a string with a value of Approved, Not approved or Skip, or in the form of YAML objects. The object(s) must contain the key result with its value as Approved or Not approved. A custom title and message can also be added using the keys title and message respectively.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterApprovedCustom
Schema
{
"example": [
"Approved",
"Not approved",
"Skip",
{
"result": "Approved"
},
{
"title": "string",
"result": "Not approved"
},
{
"title": "string",
"result": "Approved",
"message": "string"
},
[
{
"title": "string",
"result": "Approved",
"message": "string"
},
{
"title": "string",
"result": "Not approved",
"message": "string"
}
]
],
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"properties": {
"title": {
"type": "string",
"pattern": "^[\\W\\w]{1,32}$"
},
"message": {
"type": "string",
"pattern": "^[\\W\\w]{1,128}$"
},
"result": {
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
},
"required": [
"result"
],
"additionalProperties": false
}
},
{
"type": "object",
"properties": {
"title": {
"type": "string",
"pattern": "^[\\W\\w]{1,32}$"
},
"message": {
"type": "string",
"pattern": "^[\\W\\w]{1,128}$"
},
"result": {
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
},
"required": [
"result"
],
"additionalProperties": false
},
{
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Approved > Encryption at Rest

Define the minimum level of encryption required for GCP > Kubernetes Engine > Region Cluster.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine region cluster does not meet the minimum encryption level specified, it will be subject to the action specified in the GCP > Kubernetes Engine > Region Cluster > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterApprovedEncryptionAtRest
Valid Value
[
"Google managed key",
"Google managed key or higher",
"Customer managed key",
"Customer managed key or higher",
"Encryption at Rest > Customer Managed Key"
]
Schema
{
"type": "string",
"enum": [
"Google managed key",
"Google managed key or higher",
"Customer managed key",
"Customer managed key or higher",
"Encryption at Rest > Customer Managed Key"
],
"example": [
"Google managed key"
],
"default": "Google managed key or higher"
}

GCP > Kubernetes Engine > Region Cluster > Approved > Encryption at Rest > Customer Managed Key

The ID of a GCP KMS symmetric key that must be used as the encryption key for a GCP > Kubernetes Engine > Region Cluster.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine region cluster is not encrypted with the specified key, it will be subject to the action specified in the GCP > Kubernetes Engine > Region Cluster > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterApprovedEncryptionAtRestCustomerManagedKey
Schema
{
"type": "string",
"example": "projects/my-kms-project/locations/us-east1/keyRings/my-keyring/cryptoKeys/my-key",
"default": ""
}

GCP > Kubernetes Engine > Region Cluster > Approved > Regions

A list of GCP regions in which GCP Kubernetes Engine region clusters are approved for use.

The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine region cluster is created in a region that is not in the approved list, it will be subject to the action specified in the GCP > Kubernetes Engine > Region Cluster > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterApprovedRegions
Default Template Input
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineApprovedRegionsDefault\") {\n value\n }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"

GCP > Kubernetes Engine > Region Cluster > Approved > Usage

Determine whether the GCP Kubernetes Engine region cluster is allowed to exist.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine region cluster is not approved, it will be subject to the action specified in the GCP > Kubernetes Engine > Region Cluster > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterApprovedUsage
Valid Value
[
"Not approved",
"Approved",
"Approved if GCP > Kubernetes Engine > Enabled"
]
Schema
{
"type": "string",
"enum": [
"Not approved",
"Approved",
"Approved if GCP > Kubernetes Engine > Enabled"
],
"example": [
"Not approved"
],
"default": "Approved if GCP > Kubernetes Engine > Enabled"
}

GCP > Kubernetes Engine > Region Cluster > CMDB

Configure whether to record and synchronize details for the GCP Kubernetes Engine region cluster into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

CMDB controls also use the Regions policy associated with the resource. If region is not in GCP > Kubernetes Engine > Region Cluster > Regions policy, the CMDB control will delete the resource from the CMDB.

(Note: Setting CMDB to "Skip" will also pause these changes.)

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterCmdb
Category
Valid Value
[
"Skip",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine API is enabled",
"Enforce: Disabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine API is enabled",
"Enforce: Disabled"
],
"example": [
"Skip"
],
"default": "Enforce: Enabled if Kubernetes Engine API is enabled"
}

GCP > Kubernetes Engine > Region Cluster > Kubernetes Dashboard Enabled

Configure whether Kubernetes Dashboard Enabled is enabled for a Kubernetes Engine regionCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterKubernetesDashboardEnabled
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Labels

Determine the action to take when an GCP Kubernetes Engine region cluster labels are not updated based on the GCP > Kubernetes Engine > Region Cluster > Labels > * policies.

The control ensure GCP Kubernetes Engine region cluster labels include labels defined in GCP > Kubernetes Engine > Region Cluster > Labels > Template.

Labels not defined in Region Cluster Labels Template will not be modified or deleted. Setting a label value to undefined will result in the label being deleted.

See Labels for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterLabels
Valid Value
[
"Skip",
"Check: Labels are correct",
"Enforce: Set labels"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Labels are correct",
"Enforce: Set labels"
],
"example": [
"Check: Labels are correct"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Labels > Template

The template is used to generate the keys and values for GCP Kubernetes Engine region cluster.

Labels not defined in Region Cluster Labels Template will not be modified or deleted. Setting a label value to undefined will result in the label being deleted.

See Labels for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterLabelsTemplate
Default Template Input
[
"{\n project {\n turbot {\n id\n }\n }\n}\n",
"{\n defaultLabels: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineLabelsTemplate\" resourceId: \"{{ $.project.turbot.id }}\") {\n value\n }\n}\n"
]
Default Template
"{%- if $.defaultLabels.value | length == 0 %} [] {%- elif $.defaultLabels.value != undefined %}{{ $.defaultLabels.value | dump | safe }}{%- else %}{% for item in $.defaultLabels.value %}- {{ item }}{% endfor %}{% endif %}"

GCP > Kubernetes Engine > Region Cluster > Legacy Abac

Configure whether Legacy Abac is enabled for a Kubernetes Engine regionCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterLegacyAbac
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Logging

Configure whether Logging is enabled for a Kubernetes Engine regionCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterLogging
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Master Authorized Networks Config

Configure whether Master Authorized Networks Config is enabled for a Kubernetes Engine regionCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterMasterAuthorizedNetworksConfig
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Network Policy Enabled

Configure whether Network Policy Enabled is enabled for a Kubernetes Engine regionCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterNetworkPolicyEnabled
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Pod Security Policy Config

Configure whether Pod Security Policy Config is enabled for a Kubernetes Engine regionCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterPodSecurityPolicyConfig
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Regions

A list of GCP regions in which GCP Kubernetes Engine region clusters are supported for use.

Any region clusters in a region not listed here will not be recorded in CMDB.

The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterRegions
Default Template Input
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineRegionsDefault\") {\n value\n }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"

GCP > Kubernetes Engine > Region Cluster > Set Monitoring

Configure whether Set Monitoring is enabled for a Kubernetes Engine regionCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterMonitoring
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Usage

Configure the number of GCP Kubernetes Engine region clusters that can be used for this region and the current consumption against the limit.

You can configure the behavior of the control with this GCP > Kubernetes Engine > Region Cluster > Usage policy.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterUsage
Valid Value
[
"Skip",
"Check: Usage <= 85% of Limit",
"Check: Usage <= 100% of Limit"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Usage <= 85% of Limit",
"Check: Usage <= 100% of Limit"
],
"example": [
"Check: Usage <= 85% of Limit"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Cluster > Usage > Limit

Maximum number of items that can be created for this region

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterUsageLimit
Schema
{
"type": "integer",
"minimum": 0,
"default": 50
}

GCP > Kubernetes Engine > Region Cluster > Use IP Aliases

Configure whether useIpAliases is enabled for a Kubernetes Engine regionCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionClusterUseipaliases
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Node Pool > Active

Determine the action to take when an GCP Kubernetes Engine region node pool, based on the GCP > Kubernetes Engine > Region Node Pool > Active > * policies.

The 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 (GCP > Kubernetes Engine > Region Node Pool > 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 the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

See Active for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolActive
Valid Value
[
"Skip",
"Check: Active",
"Enforce: Delete inactive with 1 day warning",
"Enforce: Delete inactive with 3 days warning",
"Enforce: Delete inactive with 7 days warning",
"Enforce: Delete inactive with 14 days warning",
"Enforce: Delete inactive with 30 days warning",
"Enforce: Delete inactive with 60 days warning",
"Enforce: Delete inactive with 90 days warning",
"Enforce: Delete inactive with 180 days warning",
"Enforce: Delete inactive with 365 days warning"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Active",
"Enforce: Delete inactive with 1 day warning",
"Enforce: Delete inactive with 3 days warning",
"Enforce: Delete inactive with 7 days warning",
"Enforce: Delete inactive with 14 days warning",
"Enforce: Delete inactive with 30 days warning",
"Enforce: Delete inactive with 60 days warning",
"Enforce: Delete inactive with 90 days warning",
"Enforce: Delete inactive with 180 days warning",
"Enforce: Delete inactive with 365 days warning"
],
"example": [
"Check: Active"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Node Pool > Active > Age

The age after which the GCP Kubernetes Engine region node pool
is no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.

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 (GCP > Kubernetes Engine > Region Node Pool > 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 the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolActiveAge
Valid Value
[
"Skip",
"Force inactive if age > 1 day",
"Force inactive if age > 3 days",
"Force inactive if age > 7 days",
"Force inactive if age > 14 days",
"Force inactive if age > 30 days",
"Force inactive if age > 60 days",
"Force inactive if age > 90 days",
"Force inactive if age > 180 days",
"Force inactive if age > 365 days"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Force inactive if age > 1 day",
"Force inactive if age > 3 days",
"Force inactive if age > 7 days",
"Force inactive if age > 14 days",
"Force inactive if age > 30 days",
"Force inactive if age > 60 days",
"Force inactive if age > 90 days",
"Force inactive if age > 180 days",
"Force inactive if age > 365 days"
],
"example": [
"Force inactive if age > 90 days"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Node Pool > Active > Last Modified

The number of days since the GCP Kubernetes Engine region node pool was last modified before it is considered
inactive.

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 (GCP > Kubernetes Engine > Region Node Pool > 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 the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolActiveLastModified
Valid Value
[
"Skip",
"Active if last modified <= 1 day",
"Active if last modified <= 3 days",
"Active if last modified <= 7 days",
"Active if last modified <= 14 days",
"Active if last modified <= 30 days",
"Active if last modified <= 60 days",
"Active if last modified <= 90 days",
"Active if last modified <= 180 days",
"Active if last modified <= 365 days",
"Force active if last modified <= 1 day",
"Force active if last modified <= 3 days",
"Force active if last modified <= 7 days",
"Force active if last modified <= 14 days",
"Force active if last modified <= 30 days",
"Force active if last modified <= 60 days",
"Force active if last modified <= 90 days",
"Force active if last modified <= 180 days",
"Force active if last modified <= 365 days"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Active if last modified <= 1 day",
"Active if last modified <= 3 days",
"Active if last modified <= 7 days",
"Active if last modified <= 14 days",
"Active if last modified <= 30 days",
"Active if last modified <= 60 days",
"Active if last modified <= 90 days",
"Active if last modified <= 180 days",
"Active if last modified <= 365 days",
"Force active if last modified <= 1 day",
"Force active if last modified <= 3 days",
"Force active if last modified <= 7 days",
"Force active if last modified <= 14 days",
"Force active if last modified <= 30 days",
"Force active if last modified <= 60 days",
"Force active if last modified <= 90 days",
"Force active if last modified <= 180 days",
"Force active if last modified <= 365 days"
],
"example": [
"Active if last modified <= 90 days"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Node Pool > Approved

Determine the action to take when a GCP Kubernetes Engine region node pool is not approved based on GCP > Kubernetes Engine > Region Node Pool > 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.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolApproved
Valid Value
[
"Skip",
"Check: Approved",
"Enforce: Delete unapproved if new"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Approved",
"Enforce: Delete unapproved if new"
],
"example": [
"Check: Approved"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Node Pool > Approved > Custom

Determine whether the GCP Kubernetes Engine region node pool is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine region node pool is not approved, it will be subject to the action specified in the GCP > Kubernetes Engine > Region Node Pool > Approved policy.
See Approved for more information.

Note: The policy value must be a string with a value of Approved, Not approved or Skip, or in the form of YAML objects. The object(s) must contain the key result with its value as Approved or Not approved. A custom title and message can also be added using the keys title and message respectively.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolApprovedCustom
Schema
{
"example": [
"Approved",
"Not approved",
"Skip",
{
"result": "Approved"
},
{
"title": "string",
"result": "Not approved"
},
{
"title": "string",
"result": "Approved",
"message": "string"
},
[
{
"title": "string",
"result": "Approved",
"message": "string"
},
{
"title": "string",
"result": "Not approved",
"message": "string"
}
]
],
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"properties": {
"title": {
"type": "string",
"pattern": "^[\\W\\w]{1,32}$"
},
"message": {
"type": "string",
"pattern": "^[\\W\\w]{1,128}$"
},
"result": {
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
},
"required": [
"result"
],
"additionalProperties": false
}
},
{
"type": "object",
"properties": {
"title": {
"type": "string",
"pattern": "^[\\W\\w]{1,32}$"
},
"message": {
"type": "string",
"pattern": "^[\\W\\w]{1,128}$"
},
"result": {
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
},
"required": [
"result"
],
"additionalProperties": false
},
{
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Node Pool > Approved > Regions

A list of GCP regions in which GCP Kubernetes Engine region node pools are approved for use.

The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine region node pool is created in a region that is not in the approved list, it will be subject to the action specified in the GCP > Kubernetes Engine > Region Node Pool > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolApprovedRegions
Default Template Input
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineApprovedRegionsDefault\") {\n value\n }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"

GCP > Kubernetes Engine > Region Node Pool > Approved > Usage

Determine whether the GCP Kubernetes Engine region node pool is allowed to exist.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine region node pool is not approved, it will be subject to the action specified in the GCP > Kubernetes Engine > Region Node Pool > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolApprovedUsage
Valid Value
[
"Not approved",
"Approved",
"Approved if GCP > Kubernetes Engine > Enabled"
]
Schema
{
"type": "string",
"enum": [
"Not approved",
"Approved",
"Approved if GCP > Kubernetes Engine > Enabled"
],
"example": [
"Not approved"
],
"default": "Approved if GCP > Kubernetes Engine > Enabled"
}

GCP > Kubernetes Engine > Region Node Pool > Auto Repair

Configure whether Auto Repair is enabled for a Kubernetes Engine regionNodePool.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolAutoRepair
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Node Pool > Auto Upgrade

Configure whether Auto Upgrade is enabled for a Kubernetes Engine regionNodePool.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolAutoUpgrade
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Node Pool > CMDB

Configure whether to record and synchronize details for the GCP Kubernetes Engine region node pool into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

CMDB controls also use the Regions policy associated with the resource. If region is not in GCP > Kubernetes Engine > Region Node Pool > Regions policy, the CMDB control will delete the resource from the CMDB.

(Note: Setting CMDB to "Skip" will also pause these changes.)

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolCmdb
Category
Valid Value
[
"Skip",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine API is enabled",
"Enforce: Disabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine API is enabled",
"Enforce: Disabled"
],
"example": [
"Skip"
],
"default": "Enforce: Enabled if Kubernetes Engine API is enabled"
}

GCP > Kubernetes Engine > Region Node Pool > Regions

A list of GCP regions in which GCP Kubernetes Engine region node pools are supported for use.

Any region node pools in a region not listed here will not be recorded in CMDB.

The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolRegions
Default Template Input
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineRegionsDefault\") {\n value\n }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"

GCP > Kubernetes Engine > Region Node Pool > Usage

Configure the number of GCP Kubernetes Engine region node pools that can be used for this region and the current consumption against the limit.

You can configure the behavior of the control with this GCP > Kubernetes Engine > Region Node Pool > Usage policy.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolUsage
Valid Value
[
"Skip",
"Check: Usage <= 85% of Limit",
"Check: Usage <= 100% of Limit"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Usage <= 85% of Limit",
"Check: Usage <= 100% of Limit"
],
"example": [
"Check: Usage <= 85% of Limit"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Region Node Pool > Usage > Limit

Maximum number of items that can be created for this region

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/regionNodePoolUsageLimit
Schema
{
"type": "integer",
"minimum": 0,
"default": 5000
}

GCP > Kubernetes Engine > Regions

A list of GCP regions in which GCP Kubernetes Engine resources are supported for use.

The expected format is an array of regions names. You may use the '*' and
'?' wildcard characters.

This policy is the default value for all GCP Kubernetes Engine resources' Regions policies.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineRegionsDefault
Schema
{
"allOf": [
{
"$ref": "gcp#/definitions/regionNameMatcherList"
},
{
"default": [
"asia-east1",
"asia-east2",
"asia-northeast1",
"asia-northeast2",
"asia-south1",
"asia-southeast1",
"australia-southeast1",
"europe-north1",
"europe-west1",
"europe-west2",
"europe-west3",
"europe-west4",
"europe-west6",
"northamerica-northeast1",
"southamerica-east1",
"us-central1",
"us-east1",
"us-east4",
"us-west1",
"us-west2"
]
}
]
}

GCP > Kubernetes Engine > Zone Cluster > Active

Determine the action to take when an GCP Kubernetes Engine zone cluster, based on the GCP > Kubernetes Engine > Zone Cluster > Active > * policies.

The 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 (GCP > Kubernetes Engine > Zone 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 the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

See Active for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterActive
Valid Value
[
"Skip",
"Check: Active",
"Enforce: Delete inactive with 1 day warning",
"Enforce: Delete inactive with 3 days warning",
"Enforce: Delete inactive with 7 days warning",
"Enforce: Delete inactive with 14 days warning",
"Enforce: Delete inactive with 30 days warning",
"Enforce: Delete inactive with 60 days warning",
"Enforce: Delete inactive with 90 days warning",
"Enforce: Delete inactive with 180 days warning",
"Enforce: Delete inactive with 365 days warning"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Active",
"Enforce: Delete inactive with 1 day warning",
"Enforce: Delete inactive with 3 days warning",
"Enforce: Delete inactive with 7 days warning",
"Enforce: Delete inactive with 14 days warning",
"Enforce: Delete inactive with 30 days warning",
"Enforce: Delete inactive with 60 days warning",
"Enforce: Delete inactive with 90 days warning",
"Enforce: Delete inactive with 180 days warning",
"Enforce: Delete inactive with 365 days warning"
],
"example": [
"Check: Active"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Active > Age

The age after which the GCP Kubernetes Engine zone cluster
is no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.

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 (GCP > Kubernetes Engine > Zone 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 the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterActiveAge
Valid Value
[
"Skip",
"Force inactive if age > 1 day",
"Force inactive if age > 3 days",
"Force inactive if age > 7 days",
"Force inactive if age > 14 days",
"Force inactive if age > 30 days",
"Force inactive if age > 60 days",
"Force inactive if age > 90 days",
"Force inactive if age > 180 days",
"Force inactive if age > 365 days"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Force inactive if age > 1 day",
"Force inactive if age > 3 days",
"Force inactive if age > 7 days",
"Force inactive if age > 14 days",
"Force inactive if age > 30 days",
"Force inactive if age > 60 days",
"Force inactive if age > 90 days",
"Force inactive if age > 180 days",
"Force inactive if age > 365 days"
],
"example": [
"Force inactive if age > 90 days"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Active > Last Modified

The number of days since the GCP Kubernetes Engine zone cluster was last modified before it is considered
inactive.

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 (GCP > Kubernetes Engine > Zone 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 the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterActiveLastModified
Valid Value
[
"Skip",
"Active if last modified <= 1 day",
"Active if last modified <= 3 days",
"Active if last modified <= 7 days",
"Active if last modified <= 14 days",
"Active if last modified <= 30 days",
"Active if last modified <= 60 days",
"Active if last modified <= 90 days",
"Active if last modified <= 180 days",
"Active if last modified <= 365 days",
"Force active if last modified <= 1 day",
"Force active if last modified <= 3 days",
"Force active if last modified <= 7 days",
"Force active if last modified <= 14 days",
"Force active if last modified <= 30 days",
"Force active if last modified <= 60 days",
"Force active if last modified <= 90 days",
"Force active if last modified <= 180 days",
"Force active if last modified <= 365 days"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Active if last modified <= 1 day",
"Active if last modified <= 3 days",
"Active if last modified <= 7 days",
"Active if last modified <= 14 days",
"Active if last modified <= 30 days",
"Active if last modified <= 60 days",
"Active if last modified <= 90 days",
"Active if last modified <= 180 days",
"Active if last modified <= 365 days",
"Force active if last modified <= 1 day",
"Force active if last modified <= 3 days",
"Force active if last modified <= 7 days",
"Force active if last modified <= 14 days",
"Force active if last modified <= 30 days",
"Force active if last modified <= 60 days",
"Force active if last modified <= 90 days",
"Force active if last modified <= 180 days",
"Force active if last modified <= 365 days"
],
"example": [
"Active if last modified <= 90 days"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Approved

Determine the action to take when a GCP Kubernetes Engine zone cluster is not approved based on GCP > Kubernetes Engine > Zone 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.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterApproved
Valid Value
[
"Skip",
"Check: Approved",
"Enforce: Delete unapproved if new"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Approved",
"Enforce: Delete unapproved if new"
],
"example": [
"Check: Approved"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Approved > Custom

Determine whether the GCP Kubernetes Engine zone cluster is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine zone cluster is not approved, it will be subject to the action specified in the GCP > Kubernetes Engine > Zone Cluster > Approved policy.
See Approved for more information.

Note: The policy value must be a string with a value of Approved, Not approved or Skip, or in the form of YAML objects. The object(s) must contain the key result with its value as Approved or Not approved. A custom title and message can also be added using the keys title and message respectively.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterApprovedCustom
Schema
{
"example": [
"Approved",
"Not approved",
"Skip",
{
"result": "Approved"
},
{
"title": "string",
"result": "Not approved"
},
{
"title": "string",
"result": "Approved",
"message": "string"
},
[
{
"title": "string",
"result": "Approved",
"message": "string"
},
{
"title": "string",
"result": "Not approved",
"message": "string"
}
]
],
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"properties": {
"title": {
"type": "string",
"pattern": "^[\\W\\w]{1,32}$"
},
"message": {
"type": "string",
"pattern": "^[\\W\\w]{1,128}$"
},
"result": {
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
},
"required": [
"result"
],
"additionalProperties": false
}
},
{
"type": "object",
"properties": {
"title": {
"type": "string",
"pattern": "^[\\W\\w]{1,32}$"
},
"message": {
"type": "string",
"pattern": "^[\\W\\w]{1,128}$"
},
"result": {
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
},
"required": [
"result"
],
"additionalProperties": false
},
{
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Approved > Encryption at Rest

Define the minimum level of encryption required for GCP > Kubernetes Engine > Zone Cluster.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine zone cluster does not meet the minimum encryption level specified, it will be subject to the action specified in the GCP > Kubernetes Engine > Zone Cluster > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterApprovedEncryptionAtRest
Valid Value
[
"Google managed key",
"Google managed key or higher",
"Customer managed key",
"Encryption at Rest > Customer Managed Key"
]
Schema
{
"type": "string",
"enum": [
"Google managed key",
"Google managed key or higher",
"Customer managed key",
"Encryption at Rest > Customer Managed Key"
],
"example": [
"Google managed key"
],
"default": "Google managed key or higher"
}

GCP > Kubernetes Engine > Zone Cluster > Approved > Encryption at Rest > Customer Managed Key

The ID of a GCP KMS symmetric key that must be used as the encryption key for a GCP > Kubernetes Engine > Zone Cluster.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine zone cluster is not encrypted with the specified key, it will be subject to the action specified in the GCP > Kubernetes Engine > Zone Cluster > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterApprovedEncryptionAtRestCustomerManagedKey
Schema
{
"type": "string",
"example": "projects/my-kms-project/locations/us-east1/keyRings/my-keyring/cryptoKeys/my-key",
"default": ""
}

GCP > Kubernetes Engine > Zone Cluster > Approved > Regions

A list of GCP regions in which GCP Kubernetes Engine zone clusters are approved for use.

The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine zone cluster is created in a region that is not in the approved list, it will be subject to the action specified in the GCP > Kubernetes Engine > Zone Cluster > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterApprovedRegions
Default Template Input
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineApprovedRegionsDefault\") {\n value\n }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"

GCP > Kubernetes Engine > Zone Cluster > Approved > Usage

Determine whether the GCP Kubernetes Engine zone cluster is allowed to exist.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine zone cluster is not approved, it will be subject to the action specified in the GCP > Kubernetes Engine > Zone Cluster > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterApprovedUsage
Valid Value
[
"Not approved",
"Approved",
"Approved if GCP > Kubernetes Engine > Enabled"
]
Schema
{
"type": "string",
"enum": [
"Not approved",
"Approved",
"Approved if GCP > Kubernetes Engine > Enabled"
],
"example": [
"Not approved"
],
"default": "Approved if GCP > Kubernetes Engine > Enabled"
}

GCP > Kubernetes Engine > Zone Cluster > CMDB

Configure whether to record and synchronize details for the GCP Kubernetes Engine zone cluster into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

CMDB controls also use the Regions policy associated with the resource. If region is not in GCP > Kubernetes Engine > Zone Cluster > Regions policy, the CMDB control will delete the resource from the CMDB.

(Note: Setting CMDB to "Skip" will also pause these changes.)

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterCmdb
Category
Targets
Valid Value
[
"Skip",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine API is enabled",
"Enforce: Disabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine API is enabled",
"Enforce: Disabled"
],
"example": [
"Skip"
],
"default": "Enforce: Enabled if Kubernetes Engine API is enabled"
}

GCP > Kubernetes Engine > Zone Cluster > Kubernetes Dashboard Enabled

Configure whether Kubernetes Dashboard Enabled is enabled for a Kubernetes Engine zoneCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterKubernetesDashboardEnabled
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Labels

Determine the action to take when an GCP Kubernetes Engine zone cluster labels are not updated based on the GCP > Kubernetes Engine > Zone Cluster > Labels > * policies.

The control ensure GCP Kubernetes Engine zone cluster labels include labels defined in GCP > Kubernetes Engine > Zone Cluster > Labels > Template.

Labels not defined in Zone Cluster Labels Template will not be modified or deleted. Setting a label value to undefined will result in the label being deleted.

See Labels for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterLabels
Valid Value
[
"Skip",
"Check: Labels are correct",
"Enforce: Set labels"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Labels are correct",
"Enforce: Set labels"
],
"example": [
"Check: Labels are correct"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Labels > Template

The template is used to generate the keys and values for GCP Kubernetes Engine zone cluster.

Labels not defined in Zone Cluster Labels Template will not be modified or deleted. Setting a label value to undefined will result in the label being deleted.

See Labels for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterLabelsTemplate
Default Template Input
[
"{\n project {\n turbot {\n id\n }\n }\n}\n",
"{\n defaultLabels: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineLabelsTemplate\" resourceId: \"{{ $.project.turbot.id }}\") {\n value\n }\n}\n"
]
Default Template
"{%- if $.defaultLabels.value | length == 0 %} [] {%- elif $.defaultLabels.value != undefined %}{{ $.defaultLabels.value | dump | safe }}{%- else %}{% for item in $.defaultLabels.value %}- {{ item }}{% endfor %}{% endif %}"

GCP > Kubernetes Engine > Zone Cluster > Network Policy Enabled

Configure whether Network Policy Enabled is enabled for a Kubernetes Engine zoneCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterNetworkPolicyEnabled
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Pod Security Policy Config

Configure whether Pod Security Policy Config is enabled for a Kubernetes Engine zoneCluster.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterPodSecurityPolicyConfig
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Regions

Regions where GCP supports Kubernetes Engine Zone Cluster resouce. Guardrails updates this option as GCP expands their regional support. Unless there is an explicit requirement (e.g. accelerated regional support), it should not be set.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterRegions
Category
Default Template Input
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineRegionsDefault\") {\n value\n }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"

GCP > Kubernetes Engine > Zone Cluster > Usage

Configure the number of GCP Kubernetes Engine zone clusters that can be used for this zone and the current consumption against the limit.

You can configure the behavior of the control with this GCP > Kubernetes Engine > Zone Cluster > Usage policy.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterUsage
Targets
Valid Value
[
"Skip",
"Check: Usage <= 85% of Limit",
"Check: Usage <= 100% of Limit"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Usage <= 85% of Limit",
"Check: Usage <= 100% of Limit"
],
"example": [
"Check: Usage <= 85% of Limit"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Cluster > Usage > Limit

Maximum number of items that can be created for this zone

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneClusterUsageLimit
Targets
Schema
{
"type": "integer",
"minimum": 0,
"default": 50
}

GCP > Kubernetes Engine > Zone Node Pool > Active

Determine the action to take when an GCP Kubernetes Engine zone node pool, based on the GCP > Kubernetes Engine > Zone Node Pool > Active > * policies.

The 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 (GCP > Kubernetes Engine > Zone Node Pool > 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 the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

See Active for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolActive
Valid Value
[
"Skip",
"Check: Active",
"Enforce: Delete inactive with 1 day warning",
"Enforce: Delete inactive with 3 days warning",
"Enforce: Delete inactive with 7 days warning",
"Enforce: Delete inactive with 14 days warning",
"Enforce: Delete inactive with 30 days warning",
"Enforce: Delete inactive with 60 days warning",
"Enforce: Delete inactive with 90 days warning",
"Enforce: Delete inactive with 180 days warning",
"Enforce: Delete inactive with 365 days warning"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Active",
"Enforce: Delete inactive with 1 day warning",
"Enforce: Delete inactive with 3 days warning",
"Enforce: Delete inactive with 7 days warning",
"Enforce: Delete inactive with 14 days warning",
"Enforce: Delete inactive with 30 days warning",
"Enforce: Delete inactive with 60 days warning",
"Enforce: Delete inactive with 90 days warning",
"Enforce: Delete inactive with 180 days warning",
"Enforce: Delete inactive with 365 days warning"
],
"example": [
"Check: Active"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Node Pool > Active > Age

The age after which the GCP Kubernetes Engine zone node pool
is no longer considered active. If a create time is unavailable, the time Guardrails discovered the resource is used.

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 (GCP > Kubernetes Engine > Zone Node Pool > 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 the contrast with Approved, where if the resource appears to be Unapproved
for any reason it will be considered Unapproved.

See Active for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolActiveAge
Valid Value
[
"Skip",
"Force inactive if age > 1 day",
"Force inactive if age > 3 days",
"Force inactive if age > 7 days",
"Force inactive if age > 14 days",
"Force inactive if age > 30 days",
"Force inactive if age > 60 days",
"Force inactive if age > 90 days",
"Force inactive if age > 180 days",
"Force inactive if age > 365 days"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Force inactive if age > 1 day",
"Force inactive if age > 3 days",
"Force inactive if age > 7 days",
"Force inactive if age > 14 days",
"Force inactive if age > 30 days",
"Force inactive if age > 60 days",
"Force inactive if age > 90 days",
"Force inactive if age > 180 days",
"Force inactive if age > 365 days"
],
"example": [
"Force inactive if age > 90 days"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Node Pool > Active > Last Modified

The number of days since the GCP Kubernetes Engine zone node pool was last modified before it is considered
inactive.

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 (GCP > Kubernetes Engine > Zone Node Pool > 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 the contrast with Approved, where if the
resource appears to be Unapproved for any reason it will be considered
Unapproved.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolActiveLastModified
Valid Value
[
"Skip",
"Active if last modified <= 1 day",
"Active if last modified <= 3 days",
"Active if last modified <= 7 days",
"Active if last modified <= 14 days",
"Active if last modified <= 30 days",
"Active if last modified <= 60 days",
"Active if last modified <= 90 days",
"Active if last modified <= 180 days",
"Active if last modified <= 365 days",
"Force active if last modified <= 1 day",
"Force active if last modified <= 3 days",
"Force active if last modified <= 7 days",
"Force active if last modified <= 14 days",
"Force active if last modified <= 30 days",
"Force active if last modified <= 60 days",
"Force active if last modified <= 90 days",
"Force active if last modified <= 180 days",
"Force active if last modified <= 365 days"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Active if last modified <= 1 day",
"Active if last modified <= 3 days",
"Active if last modified <= 7 days",
"Active if last modified <= 14 days",
"Active if last modified <= 30 days",
"Active if last modified <= 60 days",
"Active if last modified <= 90 days",
"Active if last modified <= 180 days",
"Active if last modified <= 365 days",
"Force active if last modified <= 1 day",
"Force active if last modified <= 3 days",
"Force active if last modified <= 7 days",
"Force active if last modified <= 14 days",
"Force active if last modified <= 30 days",
"Force active if last modified <= 60 days",
"Force active if last modified <= 90 days",
"Force active if last modified <= 180 days",
"Force active if last modified <= 365 days"
],
"example": [
"Active if last modified <= 90 days"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Node Pool > Approved

Determine the action to take when a GCP Kubernetes Engine zone node pool is not approved based on GCP > Kubernetes Engine > Zone Node Pool > 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.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolApproved
Valid Value
[
"Skip",
"Check: Approved",
"Enforce: Delete unapproved if new"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Approved",
"Enforce: Delete unapproved if new"
],
"example": [
"Check: Approved"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Node Pool > Approved > Custom

Determine whether the GCP Kubernetes Engine zone node pool is allowed to exist.
This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine zone node pool is not approved, it will be subject to the action specified in the GCP > Kubernetes Engine > Zone Node Pool > Approved policy.
See Approved for more information.

Note: The policy value must be a string with a value of Approved, Not approved or Skip, or in the form of YAML objects. The object(s) must contain the key result with its value as Approved or Not approved. A custom title and message can also be added using the keys title and message respectively.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolApprovedCustom
Schema
{
"example": [
"Approved",
"Not approved",
"Skip",
{
"result": "Approved"
},
{
"title": "string",
"result": "Not approved"
},
{
"title": "string",
"result": "Approved",
"message": "string"
},
[
{
"title": "string",
"result": "Approved",
"message": "string"
},
{
"title": "string",
"result": "Not approved",
"message": "string"
}
]
],
"anyOf": [
{
"type": "array",
"items": {
"type": "object",
"properties": {
"title": {
"type": "string",
"pattern": "^[\\W\\w]{1,32}$"
},
"message": {
"type": "string",
"pattern": "^[\\W\\w]{1,128}$"
},
"result": {
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
},
"required": [
"result"
],
"additionalProperties": false
}
},
{
"type": "object",
"properties": {
"title": {
"type": "string",
"pattern": "^[\\W\\w]{1,32}$"
},
"message": {
"type": "string",
"pattern": "^[\\W\\w]{1,128}$"
},
"result": {
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
},
"required": [
"result"
],
"additionalProperties": false
},
{
"type": "string",
"pattern": "^(Approved|Not approved|Skip)$"
}
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Node Pool > Approved > Regions

A list of GCP regions in which GCP Kubernetes Engine zone node pools are approved for use.

The expected format is an array of regions names. You may use the '*' and '?' wildcard characters.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine zone node pool is created in a region that is not in the approved list, it will be subject to the action specified in the GCP > Kubernetes Engine > Zone Node Pool > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolApprovedRegions
Default Template Input
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineApprovedRegionsDefault\") {\n value\n }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"

GCP > Kubernetes Engine > Zone Node Pool > Approved > Usage

Determine whether the GCP Kubernetes Engine zone node pool is allowed to exist.

This policy will be evaluated by the Approved control. If a GCP Kubernetes Engine zone node pool is not approved, it will be subject to the action specified in the GCP > Kubernetes Engine > Zone Node Pool > Approved policy.

See Approved for more information.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolApprovedUsage
Valid Value
[
"Not approved",
"Approved",
"Approved if GCP > Kubernetes Engine > Enabled"
]
Schema
{
"type": "string",
"enum": [
"Not approved",
"Approved",
"Approved if GCP > Kubernetes Engine > Enabled"
],
"example": [
"Not approved"
],
"default": "Approved if GCP > Kubernetes Engine > Enabled"
}

GCP > Kubernetes Engine > Zone Node Pool > Auto Repair

Configure whether Auto Repair is enabled for a Kubernetes Engine zoneNodePool.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolAutoRepair
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Node Pool > Auto Upgrade

Configure whether Auto Upgrade is enabled for a Kubernetes Engine zoneNodePool.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolAutoUpgrade
Category
Valid Value
[
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Disabled",
"Check: Enabled",
"Enforce: Disabled",
"Enforce: Enabled"
],
"example": [
"Skip"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Node Pool > CMDB

Configure whether to record and synchronize details for the GCP Kubernetes Engine zone node pool into the CMDB.

The CMDB control is responsible for populating and updating all the attributes for that resource type in the Guardrails CMDB.
All policies and controls in Guardrails are based around the resource, so usually the CMDB policy is set to "Enforce: Enabled".

If set to Skip then all changes to the CMDB are paused - no new resources will be discovered, no updates will be made and deleted resources will not be removed.

To cleanup resources and stop tracking changes, set this policy to "Enforce: Disabled".

CMDB controls also use the Regions policy associated with the resource. If region is not in GCP > Kubernetes Engine > Zone Node Pool > Regions policy, the CMDB control will delete the resource from the CMDB.

(Note: Setting CMDB to "Skip" will also pause these changes.)

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolCmdb
Category
Valid Value
[
"Skip",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine API is enabled",
"Enforce: Disabled"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Enforce: Enabled",
"Enforce: Enabled if Kubernetes Engine API is enabled",
"Enforce: Disabled"
],
"example": [
"Skip"
],
"default": "Enforce: Enabled if Kubernetes Engine API is enabled"
}

GCP > Kubernetes Engine > Zone Node Pool > Regions

Regions where GCP supports Kubernetes Engine Zone Node Pool resouce. Guardrails updates this option as GCP expands their regional support. Unless there is an explicit requirement (e.g. accelerated regional support), it should not be set.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolRegions
Category
Default Template Input
"{\n regions: policyValue(uri:\"tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineRegionsDefault\") {\n value\n }\n}\n"
Default Template
"{% if $.regions.value | length == 0 %} [] {% endif %}{% for item in $.regions.value %}- &#39;{{ item }}&#39;&#92;n{% endfor %}"

GCP > Kubernetes Engine > Zone Node Pool > Usage

Configure the number of GCP Kubernetes Engine zone node pools that can be used for this zone and the current consumption against the limit.

You can configure the behavior of the control with this GCP > Kubernetes Engine > Zone Node Pool > Usage policy.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolUsage
Targets
Valid Value
[
"Skip",
"Check: Usage <= 85% of Limit",
"Check: Usage <= 100% of Limit"
]
Schema
{
"type": "string",
"enum": [
"Skip",
"Check: Usage <= 85% of Limit",
"Check: Usage <= 100% of Limit"
],
"example": [
"Check: Usage <= 85% of Limit"
],
"default": "Skip"
}

GCP > Kubernetes Engine > Zone Node Pool > Usage > Limit

Maximum number of items that can be created for this zone

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/zoneNodePoolUsageLimit
Targets
Schema
{
"type": "integer",
"minimum": 0,
"default": 5000
}

GCP > Turbot > Event Handlers > Logging > Sink > Compiled Filter > @turbot/gcp-kubernetesengine

A GCP logs advanced filter
used to specify a subset of log entries that will be forwarded by the
logging sink on behalf of the gcp-kubernetesEngine mod

This is a read-only policy that is used internally by Guardrails

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/kubernetesEngineEventPatterns
Schema
{
"type": "string",
"default": "((resource.type = gke_nodepool OR resource.type = gke_cluster) AND (protoPayload.authorizationInfo.permission = container.clusters.create OR protoPayload.authorizationInfo.permission = container.clusters.update OR protoPayload.authorizationInfo.permission = container.clusters.delete) AND severity>=INFO AND severity<ERROR)"
}

GCP > Turbot > Permissions > Compiled > Levels > @turbot/gcp-kubernetesengine

A calculated policy that Guardrails uses to create a compiled list of ALL permission
levels for GCP Kubernetes Engine that is used as input to
the stack that manages the Guardrails IAM permissions objects.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/gcpLevelsCompiled

GCP > Turbot > Permissions > Compiled > Service Permissions > @turbot/gcp-kubernetesengine

A calculated policy that Guardrails uses to create a compiled list of ALL
permissions for GCP Kubernetes Engine that is used as
input to the control that manages the IAM stack.

URI
tmod:@turbot/gcp-kubernetesengine#/policy/types/gcpCompiledServicePermissions