Push images to gce

[jimmykarily]

Fixes #3147

What this PR does / why we need it:

Which issue(s) this PR fixes (optional, in fixes #<issue number>(, fixes #<issue_number>, ...) format, will close the issue(s) when PR gets merged):
Fixes #

[Itxaka]

Nice!

[Itxaka]

So what I get from this is that there is no regions on GCE then? Uploading an image makes it available everywhere?

[jimmykarily]

user-data also works:

instance-20250228-095741:/home/kairos # cat /etc/kairos-release 
KAIROS_ARCH="amd64"
KAIROS_BUG_REPORT_URL="https://github.com/kairos-io/kairos/issues"
KAIROS_FAMILY="suse"
KAIROS_FLAVOR="opensuse"
KAIROS_FLAVOR_RELEASE="leap-15.6"
KAIROS_FRAMEWORK_VERSION="v2.16.1"
KAIROS_HOME_URL="https://github.com/kairos-io/kairos"
KAIROS_ID="kairos"
KAIROS_ID_LIKE="kairos-core-opensuse-leap-15.6"
KAIROS_IMAGE_LABEL="leap-15.6-core-amd64-generic-3.3.1-71-gad983b4"
KAIROS_MODEL="generic"
KAIROS_NAME="kairos-core-opensuse-leap-15.6"
KAIROS_REGISTRY_AND_ORG="quay.io/kairos"
KAIROS_RELEASE="3.3.1-71-gad983b4"
KAIROS_TARGETARCH="amd64"
KAIROS_VARIANT="core"
KAIROS_VERSION="3.3.1-71-gad983b4"
instance-20250228-095741:/home/kairos # 

It's set as metadata when creating the VM:

(docs pending)

[jimmykarily]

So what I get from this is that there is no regions on GCE then? Uploading an image makes it available everywhere?

there are "locations" but images are a global resource: https://cloud.google.com/sdk/gcloud/reference/compute/images/list (no mention of location anywhere)

[jimmykarily]

Caution: Publicly shared images do not appear in the images list for users. Users must know the image name explicitly. Users cannot rely on getting the information by making an images.list request.

https://cloud.google.com/compute/docs/images/managing-access-custom-images

[jimmykarily]

I can't find a way to search for images in the UI. The only thing that works (which matches the limitation mentioned in the above comment) is to manually point to the image in the command line:

gcloud --project  <myproject> compute instances create kairos-vm-test --image=projects/palette-kairos/global/images/kairos-ubuntu-24-04-core-amd64-generic-v3-2-1 --image-project=palette-kairos

This requires the user to know the full image "path". If we can't find any better way, we should just make sure our documentation always points to the current public image. 🤷 Strange UX from google.

[jimmykarily]

It may need something more to make the image available to more "zones". I'll look into it.

[jimmykarily]

--storage-location=STORAGE_LOCATION
    Specifies a Cloud Storage location, either regional or multi-regional, where image content is to be stored. If not specified, the multi-region location closest to the source is chosen automatically. 

https://cloud.google.com/sdk/gcloud/reference/compute/images/import

We should try "global" or "asia,eu,us" according to chatgpt. Let's see.

[jimmykarily]

--storage-location=STORAGE_LOCATION
    Specifies a Cloud Storage location, either regional or multi-regional, where image content is to be stored. If not specified, the multi-region location closest to the source is chosen automatically. 

https://cloud.google.com/sdk/gcloud/reference/compute/images/import

We should try "global" or "asia,eu,us" according to chatgpt. Let's see.

"storage-location" is an argument of the "gcloud compute images import" command not "gcloud migration vms image-imports create" . Images are a global resource anyway and only latency and costs are different by adding more regions/zones/locations/whatever.