no guest kernel and rootfs image after deployment

[kouzili]

Describe the bug
I'm using arm64 platforms, the first thing I've got is that the confidential-containers/operator on quay.io has no arm64 support. the latest/main tag supports arm64, though, it does not prepare the needed /opt/kata/share/kata-containers/vmlinuz-confidential.container and /opt/kata/share/kata-containers/kata-containers-confidential.img. Is it normal? thx~

To Reproduce
Steps to reproduce the behavior:

1. Go to '...'
2. Click on '....'
3. Scroll down to '....'
4. See error

Describe the results you expected
A clear and concise description of what you expected to happen.

Describe the results you received:
A clear and concise description of what happened.

Additional context
Add any other context about the problem here.

[stevenhorsman]

Hi @kouzili, a couple of comments:

the first thing I've got is that the confidential-containers/operator on quay.io has no arm64 support. the latest/main tag supports arm64, though

arm64 build for the operator image was only added in December (#474), so if you are referring to release images (ie. 0.11.0 tag) not having arm64 support that is expected, but there should be an arm 0.12.0 tag soon.

it does not prepare the needed /opt/kata/share/kata-containers/vmlinuz-confidential.container and /opt/kata/share/kata-containers/kata-containers-confidential.img. Is it normal?

These artifacts come from the kata-deploy payload, not the operator image and I can confirm that there isn't arm64 versions of the confidential image, or kernel yet, so this is expected behaviour.