pub struct InstancePoolTemplateRequestInput {
pub flavor: String,
pub architecture: Option<String>,
pub image: Option<String>,
pub addresses: Option<Vec<AddressRequestInput>>,
pub security_groups: Option<Vec<String>>,
pub floating_ip_assignment: Option<InstancePoolTemplateRequestInputFloatingIpAssignment>,
pub user_data: Option<String>,
pub metadata: Option<MetadataInput>,
pub tags: Option<TagsInput>,
pub iam_role: Option<String>,
pub volumes: Option<Vec<InstanceVolumeInput>>,
}Fields§
§flavor: StringRegional flavor reference (UUID, CRN or exact name).
architecture: Option<String>§image: Option<String>Image to clone each replica’s boot disk from. Accepts the same four forms instance create does: an architecture-qualified CRN, an image id, name:version, or a bare name. Unlike instance create, the reference is resolved ONCE, when the pool is created, and the resulting image id is what every replica boots — including replacements spawned months later. A tag re-resolved per replica would let a heal boot a newer build than its siblings, and a pool whose members are quietly not identical is the premise of the primitive breaking silently. To move a pool to a new build, change the template.
addresses: Option<Vec<AddressRequestInput>>Address families allocated per member; fixed addresses are not allowed.
security_groups: Option<Vec<String>>Security group selectors applied to every member interface.
floating_ip_assignment: Option<InstancePoolTemplateRequestInputFloatingIpAssignment>Per-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<MetadataInput>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: Option<String>IAM role reference from the same account (UUID, CRN or exact name). PassRole and instance trust authorization apply.
volumes: Option<Vec<InstanceVolumeInput>>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.