Closed liudalibj closed 3 months ago
Hi @liudalibj. Thanks for your PR.
I'm waiting for a openshift 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.
@liudalibj thanks for this.. Can you also please update the config to add this stanza and update the commit description accordingly. Since the process requires transforming the plaintext via butane, I don't see any benefit of separate commits. But please add the description of the changes to the commit message.
allowed_annotations = [
"io.kubernetes.cri-o.Devices",
]
Complete config
[crio.runtime.runtimes.kata-remote]
runtime_path = "/usr/bin/containerd-shim-kata-v2-tp"
runtime_type = "vm"
runtime_root = "/run/vc"
runtime_config_path = "/opt/kata/configuration-remote.toml"
privileged_without_host_devices = true
runtime_pull_image = true
allowed_annotations = [
"io.kubernetes.cri-o.Devices",
]
Please also add the following to the commit message Fixes: #KATA-3155
/ok-to-test
@liudalibj: 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 | 982220541019493266d313764eb949e452db9a5b | link | false | /test sandboxed-containers-operator-e2e |
ci/prow/check | 982220541019493266d313764eb949e452db9a5b | link | false | /test check |
Full PR test history. Your PR dashboard.
runtime_pull_image = true
to 50-kata-remote config file- Description of the problem which is fixed/What is the use case
CAA latest main branch codes are base on kata-agent main branch code already, it will always pull image in guest. Without this change the CAA latest main branch codes can't work well in OCP cluster, the error logs when create a peerpod look like:
related code https://github.com/confidential-containers/cloud-api-adaptor/blob/main/src/cloud-api-adaptor/pkg/adaptor/proxy/service.go#L85C18-L85C146
- What I did
add support for pull-in-guest method
v1.29.5+29c95f3
so we need enable the pull-in-guest function in crio config file
50-kata-remote
:- How to verify it
[root@bastion-ocp-cn-new ~]# oc get nodes NAME STATUS ROLES AGE VERSION control-plane-ocp-cn-new-0.ocp-cn-new.test-ocp-cn-new.coco Ready control-plane,master 6d20h v1.29.5+29c95f3 control-plane-ocp-cn-new-1.ocp-cn-new.test-ocp-cn-new.coco Ready control-plane,master 6d20h v1.29.5+29c95f3 control-plane-ocp-cn-new-2.ocp-cn-new.test-ocp-cn-new.coco Ready control-plane,master 6d20h v1.29.5+29c95f3 worker-ocp-cn-new-0.ocp-cn-new.test-ocp-cn-new.coco Ready kata-oc,worker 6d20h v1.29.5+29c95f3 worker-ocp-cn-new-1.ocp-cn-new.test-ocp-cn-new.coco Ready kata-oc,worker 6d20h v1.29.5+29c95f3 [root@bastion-ocp-cn-new ~]#
quay.io/confidential-containers/cloud-api-adaptor:dev-0480804f8f7d06202a5a18fef3a966ec6e4e59c7
- Description for the changelog
add " runtime_pull_image = true" to "50-kata-remote" file to use the pull-in-guest function from crio.