Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Peer-pods: switch runtime class name to 'kata-remote' instead of 'kata… #346

Merged
merged 1 commit into from Oct 17, 2023

Conversation

littlejawa
Copy link
Contributor

@littlejawa littlejawa commented Oct 6, 2023

Referencing "confidential containers" for the peer-pods runtime is unneeded, and will probably cause confusion in the long run.

Fixes: KATA-2465

spec:
config:
ignition:
version: 2.2.0
storage:
files:
- contents:
source: data:text/plain;charset=utf-8;base64,W2NyaW8ucnVudGltZS5ydW50aW1lcy5rYXRhLXJlbW90ZS1jY10KIHJ1bnRpbWVfcGF0aCA9ICIvdXNyL2Jpbi9jb250YWluZXJkLXNoaW0ta2F0YS12Mi10cCIKIHJ1bnRpbWVfdHlwZSA9ICJ2bSIKIHJ1bnRpbWVfcm9vdCA9ICIvcnVuL3ZjIgogcnVudGltZV9jb25maWdfcGF0aCA9ICIvb3B0L2thdGEvY29uZmlndXJhdGlvbi1yZW1vdGUudG9tbCIKIHByaXZpbGVnZWRfd2l0aG91dF9ob3N0X2RldmljZXMgPSB0cnVlCg==
source: data:text/plain;charset=utf-8;base64,W2NyaW8ucnVudGltZS5ydW50aW1lcy5rYXRhLXJlbW90ZV0KIHJ1bnRpbWVfcGF0aCA9ICIvdXNyL2Jpbi9jb250YWluZXJkLXNoaW0ta2F0YS12Mi10cCIKIHJ1bnRpbWVfdHlwZSA9ICJ2bSIKIHJ1bnRpbWVfcm9vdCA9ICIvcnVuL3ZjIgogcnVudGltZV9jb25maWdfcGF0aCA9ICIvb3B0L2thdGEvY29uZmlndXJhdGlvbi1yZW1vdGUudG9tbCIKIHByaXZpbGVnZWRfd2l0aG91dF9ob3N0X2RldmljZXMgPSB0cnVlCg==
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This is :

[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

Still using the -tp suffix for a GA feature... I seem to recall a discussion about renaming the binary as well to something like /usr/bin/containerd-shim-kata-remote-v2 . @bpradipt ?

Anyway, this change would belong to another PR since the current name in the RPM is still -tp.

@littlejawa
Copy link
Contributor Author

/hold
Seems we have issues in tests - looking into it

@openshift-ci openshift-ci bot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 6, 2023
Copy link
Member

@gkurz gkurz left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm . Thanks @littlejawa !

@littlejawa
Copy link
Contributor Author

/unhold
The problem was not related to this PR - we were testing with a wrong CAA image

@openshift-ci openshift-ci bot removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 9, 2023
Copy link
Contributor

@bpradipt bpradipt left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2023
@bpradipt bpradipt changed the title Peer-pods: swith runtime class name to 'kata-remote' instead of 'kata… Peer-pods: switch runtime class name to 'kata-remote' instead of 'kata… Oct 17, 2023
@bpradipt
Copy link
Contributor

@littlejawa nit: swith -> switch in the commit message

…a-remote-cc'

Fixes: KATA-2465

Signed-off-by: Julien Ropé <jrope@redhat.com>
@openshift-ci openshift-ci bot removed the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2023
@gkurz
Copy link
Member

gkurz commented Oct 17, 2023

/lgtm

@openshift-ci openshift-ci bot added the lgtm Indicates that a PR is ready to be merged. label Oct 17, 2023
@gkurz gkurz merged commit c4d1fd9 into openshift:devel Oct 17, 2023
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants