Kata containers: support for firecracker - #13373
Conversation
- Updated download URLs to fetch the kata-static<...>.zst files from github repo. - Added zstd package in kata-continers role. - Updated version checksums to match the new release files.
…ainers - roles/container-engine/containerd: Add support for the devmapper snapshotter plugin (requires a secondary block device) and register the kata-fc runtime. - roles/container-engine/kata-containers: Enable Firecracker hypervisor configuration and add Molecule tests for the kata-fc runtime. - roles/kubernetes-apps/container_runtimes/kata_containers: Add the kata-fc RuntimeClass manifest.
|
Welcome @ChillRedChilli! |
|
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: ChillRedChilli The full list of commands accepted by this bot can be found here. DetailsNeeds approval from an approver in each of these files:Approvers can indicate their approval by writing |
|
Hi @ChillRedChilli. Thanks for your PR. I'm waiting for a kubernetes-sigs member to verify that this patch is reasonable to test. If it is, they should reply with Regular contributors should join the org to skip this step. Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. DetailsInstructions 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. |
| sampling_ratio = {{ containerd_tracing_sampling_ratio }} | ||
| service_name = "{{ containerd_tracing_service_name }}" | ||
| {% endif %} | ||
|
|
There was a problem hiding this comment.
There was a problem hiding this comment.
There was a problem hiding this comment.
| - container-engine | ||
| - validate-container-engine | ||
|
|
||
| - name: Container Manager |
There was a problem hiding this comment.
I changed the execution order to run the Container Manager block before the Container runtimes. This is necessary because the kata-containers role (when using Firecracker) depends on containerd being already installed and configured with devmapper.
|
We currently don't have CI support for kata containers (we used to, but it might have been disabled because it was failing; I'd prefer to restore that support first). Otherwise, we won't be able to verify if this feature is working properly. |
|
@tico88612 I understand completely. Is there an open issue or PR tracking this problem? I'd like to help if possible. |
|
maybe #10137, however, the CI architecture has changed a lot during this time, so the original code might not work anymore. |
What type of PR is this?
/kind feature
What this PR does / why we need it:
This PR introduces support for the Firecracker hypervisor via Kata Containers.
Specifically, this PR:
.zstarchives.Which issue(s) this PR fixes:
Fixes #8832
Special notes for your reviewer:
The containerd devmapper snapshotter plugin requires a secondary block device. I implemented a workaround in
roles/container-engine/kata-containers/molecule/default/prepare.ymlbased on the kata-containers guide for configuring Firecracker.The workaround creates a 20GB sparse file and binds it to a loop device (
/dev/vdb). This simulates the required disk fordevmapperduring the kata-containers tests.Does this PR introduce a user-facing change?: