Chao Wu
Chao Wu
After several months of work, we have pushed all the fundamental code for rust runtime and optional built-in vmm dragonball. And we have established CI for runtime-rs, which you could...
This pull request introduces more unit tests for Dragonball.
This bug is found in the CI test `k8s-nginx-connectivity.bats` How to reproduce: 1. create deplyment:kubectl create -f deployment.yaml ``` apiVersion: apps/v1 kind: Deployment metadata: name: nginx-deployment spec: selector: matchLabels: app:...
This bug is found in the CI test `k8s-inotify.bats` How to reproduce: 1. create configmap: kubectl apply -f inotify-configmap.yaml ``` apiVersion: v1 data: config.toml: |- foo original... kind: ConfigMap metadata:...
This bug is found in CI test `k8s-empty-dirs.bats` How to reproduce: 1. kubectl create -f "pod-empty-dir.yaml" ``` apiVersion: v1 kind: Pod metadata: name: sharevol-kata spec: terminationGracePeriodSeconds: 0 runtimeClassName: kata containers: ...
This bug is found in the `k8s-copy-file.bats` CI test. How to reproduce the error : 1. create the pod: kubectl create -f pod.yaml ``` pod.yaml apiVersion: v1 kind: Pod metadata:...
Since runtime-rs enable cpu resize ability, we could try to enable k8s cpu ns test cases. fixes: #5391 Depends-on:github.com/kata-containers/kata-containers#6009 Signed-off-by: Chao Wu
Currently, fooloose k8s CI is only solved in x86_64 runtime-rs. We should exclude it for now in aarch64 in order not to block arm dragonball ci.
Since runtime-rs enable cpu resize ability, we could try to enable k8s-cpu-ns test case.
According to https://github.com/kata-containers/kata-containers/blob/main/docs/Developer-Guide.md#capturing-kernel-boot-logs, ``` Set enable_debug = true in the [hypervisor.qemu] and [runtime] sections ``` this could enable the kernel boot logs but right now we automatically add `console=ttyS1 agent.log_vport=1025`...