-
Notifications
You must be signed in to change notification settings - Fork 60
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
ccruntime: Improvements on the runtime classes we deploy #420
Changes from all commits
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -20,20 +20,23 @@ patches: | |
path: /spec/config/runtimeClasses | ||
value: | ||
- name: "kata-clh" | ||
snapshotter: "nydus" | ||
snapshotter: "" | ||
pulltype: "" | ||
- name: "kata-qemu" | ||
snapshotter: "nydus" | ||
snapshotter: "" | ||
pulltype: "" | ||
- name: "kata-qemu-coco-dev" | ||
snapshotter: "nydus" | ||
pulltype: "guest-pull" | ||
- name: "kata-qemu-tdx" | ||
snapshotter: "nydus" | ||
pulltype: "" | ||
pulltype: "guest-pull" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Hi @fidencio ! We don't test TDX/SEV/SNP with CRI-O so I left this empty on purpose. But it was a mistake, we better have it set to guest-pull anyway, hence, thanks for the fix! BTW, do you plan to test TDX + CRI-O? There is this #409 and I asked on last CI meeting if platform folks would like to test with CRI-O (I didn't get a 'yes' nor 'no'...) There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Right now we're struggling to have machines available to test. There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Got it. yeah, it would be trick to use same machine to containerd and cri-o and keep switching the configurations.... |
||
- name: "kata-qemu-sev" | ||
snapshotter: "nydus" | ||
pulltype: "" | ||
pulltype: "guest-pull" | ||
- name: "kata-qemu-snp" | ||
snapshotter: "nydus" | ||
pulltype: "" | ||
pulltype: "guest-pull" | ||
- op: add | ||
path: /spec/config/defaultRuntimeClassName | ||
value: "kata-qemu" | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Hey, this was on my TODO list, thanks!
I plan to create a job to test that runtimeclass too: #409 . But let me know if you are already working on that.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I am not working on that, just had to add this for a personal test earlier Today, and shared as I had that done already.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
@fidencio might I ask why on TEE you want nydus and on non-TEE you don't? Also you mentioned in kata there are the defaults, is it possible to rely on those defaults and not setting it here? (would empty string result in using the default or is this not technically possible?)