Schemas

Specification of the minimum and maximum replicas for the Instance group, and the cooldown interval between two scaling events.

Specification of the Load Balancer linked to the Instance group.

Instance group ID.

Project ID of the Instance group.

Name of the Instance group.

Instance group tags.

Template ID (ID of the Instance template to attach to the Instance group).

Any configuration errors for dependencies (Load Balancer, Private Network, Instance template etc.).

Date on which the Instance group was created. (RFC 3339 format)

Date on which the Instance group was last updated. (RFC 3339 format)

Zone for this resource.

Instance group event ID.

Log source.

The severity of the log.

Log title.

Date and time of the log. (RFC 3339 format)

Full text of the log.

Scaling policy ID.

Name of scaling policy.

Managed metric to use for this policy. These are available by default in Cockpit without any configuration or node_exporter. The chosen metric forms the basis of the condition that will be checked to determine whether a scaling action should be triggered.

Action to execute when the metric-based condition is met.

How to use the number defined in value when determining by how many Instances to scale up/down.

Number representing the magnitude of the scaling action to take for the Instance group.

Priority of this policy compared to all other scaling policies. The lower the number, the higher the priority (higher priority will be processed sooner in the order).

Instance group ID related to this policy.

Zone for this resource.

ID of Instance template resource.

Name of Instance commercial type.

Instance image ID. Can be an ID of a marketplace or personal image. This image must be compatible with volume and commercial_type template.

Template of Instance volume.

List of tags for the Instance template.

Instance security group ID (optional).

Instance placement group ID. This is optional, but it is highly recommended to set a preference for Instance location within Availability Zone.

Number of flexible IPv4 addresses to attach to the new Instance.

Number of flexible IPv6 addresses to attach to the new Instance.

ID of the Project containing the Instance template resource.

Name of Instance template.

Private Network IDs to attach to the new Instance.

Status of Instance template.

Cloud-config file must be passed in Base64 format. Cloud-config files are special scripts designed to be run by the cloud-init process. These are generally used for initial configuration on the very first boot of a server.

Date on which the Instance template was created. (RFC 3339 format)

Date on which the Instance template was last updated. (RFC 3339 format)

Zone for this resource.

Paginated list of Instance groups.

Count of all Instance groups matching the requested criteria.

Paginated list of Instance groups.

Count of all Instance groups matching the requested criteria.

Paginated list of policies.

Count of all policies matching the requested criteria.

Count of all templates matching the requested criteria.

Paginated list of Instance templates.