Using image family

All newly published versions since the end of 2021 support the image family attribute. Using predictable image family names makes it easier to deploy the newest image of given product's major version, because you no longer need to list all available images to see what is available. Instead, you can simply say "deploy newest image of FortiGate 7.0". The image family name consists of [product name]-[major version without dot]-[licensing option (if available)]

The following lists image families available at the time of writing:

• fortigate-64-byol
• fortigate-64-payg
• fortimanager-70
• fortianalyzer-70
• fortigate-70-byol
• fortigate-70-payg
• fortigate-70 (Do not use this image family.)
• fortigate-72-byol
• fortigate-72-payg

Using image family with gcloud

gcloud compute instances create my-fortigate \
  --machine-type=e2-micro \
  --image-family=fortigate-64-byol --image-project=fortigcp-project-001 \
  --can-ip-forward \
  --network-interface="network=default"

Using image family with Terraform

data "google_compute_image" "fgt_image" {
  project = "fortigcp-project-001"
  family  = "fortigate-72-byol"
}

resource "google_compute_instance" "my_fortigate" {
  name         = "my-fortigate"
  machine_type = "e2-micro"
  can_ip_forward = true
  boot_disk {
    initialize_params {
      image = data.google_compute_image.fgt_image.self_link
    }
  }
  network_interface {
    access_config {
    }
  }
}

Using image family with Deployment Manager

resources:
- name: my-fortigate
  type: compute.v1.instance
  properties:
    zone: europe-west6-b
    machineType: zones/europe-west6-b/machineTypes/e2-micro
    disks:
    - deviceName: boot
      type: PERSISTENT
      boot: true
      autoDelete: true
      initializeParams:
        sourceImage: projects/fortigcp-project-001/global/images/family/fortigate-64-byol
        diskSizeGb: 10.0
    networkInterfaces:
    - network: global/networks/default
      accessConfigs:
      - name: External NAT
        type: ONE_TO_ONE_NAT