change proxmox ve image output format to raw from qcow2

[stenwt]

Change description

Changes proxmox image output format from qcow2, which proxmox does not accept, to raw, which it does

Related issues

• Fixes proxmox ve builds qcow2 images, which aren't compatible with proxmox #1635

Additional context

log output after change:

proxmox-iso.ubuntu-2404: output will be in this color.

==> proxmox-iso.ubuntu-2404: Retrieving ISO
==> proxmox-iso.ubuntu-2404: Trying https://releases.ubuntu.com/noble/ubuntu-24.04.1-live-server-amd64.iso
==> proxmox-iso.ubuntu-2404: Trying https://releases.ubuntu.com/noble/ubuntu-24.04.1-live-server-amd64.iso?checksum=sha256%3Ae240e4b801f7bb68c20d1356b60968ad0c33a41d00d828e74ceb3364a0317be9
==> proxmox-iso.ubuntu-2404: https://releases.ubuntu.com/noble/ubuntu-24.04.1-live-server-amd64.iso?checksum=sha256%3Ae240e4b801f7bb68c20d1356b60968ad0c33a41d00d828e74ceb3364a0317be9 => /home/sten/.cache/packer/85d1bf86e5e0ecdd6e91515a63cc10bdab146dca.iso
==> proxmox-iso.ubuntu-2404: Creating VM
==> proxmox-iso.ubuntu-2404: No VM ID given, getting next free from Proxmox
==> proxmox-iso.ubuntu-2404: Starting VM
==> proxmox-iso.ubuntu-2404: Starting HTTP server on port 8149
==> proxmox-iso.ubuntu-2404: Waiting 10s for boot

[linux-foundation-easycla]

• ✅login: stenwt / (721c7be)

The committers listed above are authorized under a signed CLA.

[k8s-ci-robot]

Welcome @stenwt!

It looks like this is your first PR to kubernetes-sigs/image-builder 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/image-builder has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[k8s-ci-robot]

Hi @stenwt. Thanks for your PR.

I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by:
Once this PR has been reviewed and has the lgtm label, please assign mboersma for approval. For more information see the Kubernetes Code Review Process.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[mboersma]

/ok-to-test

[AverageMarcus]

@mcbenjemaa as you introduced the format initially are you able to comment on this? I'm not sure which is correct but I know the Proxmox builds have been previously working so curious as to why this PR is needed now.

[mcbenjemaa]

@mcbenjemaa as you introduced the format initially are you able to comment on this? I'm not sure which is correct but I know the Proxmox builds have been previously working so curious as to why this PR is needed now.

On the contrary, the format qcow2 is fine and works with Proxmox VE.
Perhaps, there’s something different in your setup.
therefore, I advise to add a variable for the disk format.

Format qcow2 makes more sense, and is a bit faster when cloning images. When we provision clusters with CAPI.