pub struct InstancePoolTemplate {
pub addresses: Option<Vec<AddressRequest>>,
pub security_groups: Vec<ResourceRef>,
pub floating_ip_assignment: InstancePoolTemplateFloatingIpAssignment,
pub user_data: Option<String>,
pub metadata: Option<Metadata>,
pub tags: Option<Tags>,
pub iam_role: InstancePoolTemplateIamRole,
pub volumes: Option<Vec<InstanceVolume>>,
pub flavor: ResourceRef,
pub image: InstancePoolTemplateImage,
}Fields§
§addresses: Option<Vec<AddressRequest>>Address families allocated on the member’s sole interface. Fixed addresses are not allowed.
security_groups: Vec<ResourceRef>§floating_ip_assignment: InstancePoolTemplateFloatingIpAssignmentPer-member public floating IP assignment. Explicit families require addresses and internet routes in every selected subnet.
user_data: Option<String>Base64-encoded user data (cloud-init), stamped on every replica.
metadata: Option<Metadata>Tags stamped on every instance this template launches. These are the replicas’ tags, not the pool’s — the pool’s own labels are the top-level tags, and the two are independent. Changing them affects FUTURE launches only. The instances already running keep the tags they were launched with, so between the change and a refresh the pool holds members carrying two different tag sets; stale_instance_count is how many are still on the old one. POST /v1/instance-pools/{pool_id}/refresh rolls them onto the current template.
iam_role: InstancePoolTemplateIamRoleRole assigned to replicas, or null when none is configured.
volumes: Option<Vec<InstanceVolume>>Per-replica disks, the boot disk included — mark it with boot: true. Each new replica receives the configured provisioned performance. Omitted performance uses the included allowance. Existing volumes and snapshot schedules are not supported in pool templates.
flavor: ResourceRef§image: InstancePoolTemplateImageSource image pinned until the template is replaced, or null when no image is selected.