azurelinux-3 images have a 5GB disk by default which easily hits `NodeHasDiskPressure`

[nojnhuh]

Environment

• Make target: make build-azure-sig-azurelinux-3-gen2
• Run using container image? (Y/N): N
• Environment vars:

PACKER_VAR_FILES=/home/jon/github/image-builder/jon/k8s-version.json
PACKER_FLAGS=-force
RESOURCE_GROUP_NAME=cluster-api-gallery
GALLERY_NAME=ClusterAPI
AZURE_LOCATION=uksouth

• Vars file: (/home/jon/github/image-builder/jon/k8s-version.json)

{
  "kubernetes_semver": "v1.34.1",
  "kubernetes_series": "v1.34",
  "kubernetes_deb_version": "1.34.1-1.1",
  "kubernetes_rpm_version": "1.34.1",
  "sig_image_version": "1.34.1",
  "containerd_version": "2.1.4",
  "containerd_sha256": "316d510a0428276d931023f72c09fdff1a6ba81d6cc36f31805fea6a3c88f515",
  "runc_version": "1.3.0",
  "runc_sha256": "028986516ab5646370edce981df2d8e8a8d12188deaf837142a02097000ae2f2"
}

What steps did you take and what happened?

Running with the above parameters produces an image with a 5GB OS disk. Creating a cluster with CAPZ produces nodes that hit the NodeHasDiskPressure condition after installing just cloud-provider-azure and Calico for CNI.

capi@aso-12480-controlplane-7gnht [ ~ ]$ df -h /
Filesystem      Size  Used Avail Use% Mounted on
/dev/sda3       4.3G  4.0G  113M  98% /

What did you expect to happen?

The default disk size for the image is enough to satisfy basic cluster components.

Relevant log output

The issue probably has more to do with the base image also having a small default size. The ID of that image is reflected in the logs:

Log Output

==> azure-arm.sig-azurelinux-3-gen2:  -> SourceImageName: '/subscriptions/4695d249-9812-4866-9f9a-5e3b26c74fe4/providers/Microsoft.Compute/locations/uksouth/publishers/MicrosoftCBLMariner/ArtifactTypes/vmimage/offers/azure-linux-3/skus/azure-linux-3-gen2/versions/latest'

Anything else you would like to add?

---

/kind bug