podvm: disable cloud-init unsafe modules for CoCo

[snir911]

this is executed when CONFIDENTIAL_COMPUTE_ENABLED=yes or based on the EXPLICIT_adapt_cloud_init value, if set

in either case, this is currently disabled for the libvirt provider

Fixes: KATA-3269

[gkurz]

@snir911 what's the tmporary change commit for ?

[snir911]

tmporary change was to test wheter this is works with libvirt provider, currently thanks to @ajayvic it seems to be failing so i removed this patch for now

[  OK  ] Reached target Cloud-init target.
         Starting Agent Protocol Forwarder...
         Starting Record Runlevel Change in UTMP...
[  OK  ] Finished Record Runlevel Change in UTMP.
[FAILED] Failed to start Agent Protocol Forwarder.
See 'systemctl status agent-protocol-forwarder.service' for details.
[  OK  ] Started Confidential Data Hub TTRPC API Server.

[bpradipt]

/lgtm

[openshift-ci]

@snir911: The following tests failed, say /retest to rerun all failed tests or /retest-required to rerun all mandatory failed tests:

Test name	Commit	Details	Required	Rerun command
ci/prow/sandboxed-containers-operator-e2e	1b74591	link	false	/test sandboxed-containers-operator-e2e
ci/prow/check	1b74591	link	false	/test check

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[gkurz]

Under the assumption that the content of 99_coco_only_allow.cfg is correct, the patch looks good to me.

Thanks @snir911 !