mirror of
https://github.com/kata-containers/kata-containers.git
synced 2025-10-21 20:08:54 +00:00
72ef82368c3e40d854b2c7580c9dba7fc52ffcef
35 Commits
| Author | SHA1 | Message | Date | |
|---|---|---|---|---|
stevenhorsman
|
ebf9d2725a |
kata-deploy: Add remote shim
- Add remote to the list of shims in kata-deploy and kata-cleanup Signed-off-by: stevenhorsman <steven@uk.ibm.com> |
||
Liu Wenyuan
|
14d8790d83 |
kata-deploy: Add StratoVirt support to deploy process
Allow kata-deploy process to pull StratoVirt from release binaries, and add them as a part of kata release. Fixes: #7794 Signed-off-by: Liu Wenyuan <liuwenyuan9@huawei.com> |
||
Fabiano Fidêncio
|
a93fdb014b |
kata-deploy-stable: Adapt to what we're using in the stable branch
This is basically to make sure that folks trying to use the kata-deploy script from the main branch, to deploy **stable** kata-deploy images, do not have a hard time. Fixes: #7194 Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com> |
||
Wainer dos Santos Moschetta
|
4af78be13a |
kata-deploy: re-format kata-[deploy|cleanup].yaml
The .tests/integration/kubernetes/gh-run.sh script run `yq write` a couple of times to edit the kata-[deploy|cleanup].yaml, resulting on the file being formatted again. This is annoying because leaves the git tree dirty. Signed-off-by: Wainer dos Santos Moschetta <wainersm@redhat.com> |
||
Jeremi Piotrowski
|
3230dec950 |
kata-deploy: Use host's systemctl
when interacting with systemd. We have occasionally faced issues with compatibility between the systemctl version used inside the kata-deploy container and the systemd version on the host. Instead of using a containerized systemctl with bind mounted sockets, nsenter the host and run systemctl from there. This provides less coupling between the kata-deploy container and the host. Fixes: #7511 Signed-off-by: Jeremi Piotrowski <jpiotrowski@microsoft.com> |
||
|
Fabiano Fidêncio
|
0e157be6f2 |
kata-deploy: Allow runtimeclasses to be created by the daemonset
Let's allow the daemonset to create the runtimeclasses, which will decrease one manual step a user of kata-deploy should take, and also help us in the Confidential Containers land as the Operator can just delegate it to this script. Fixes: #7409 Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com> |
||
|
Fabiano Fidêncio
|
a274333248 |
kata-deploy: Change default values of DEBUG
This can be easily done as there was no official release with the previous values. The reason we're doing so is because when using `yq` to replace the value, even when forcing `--tag '!!str' "yes"`, the content is placed without quotes, causing errors in our CI. While here, we're also removing the fallback value for DEBUG, as it is **always** set in the kata-deploy.yaml file. Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com> |
||
|
Fabiano Fidêncio
|
a56f96bb2b |
kata-deploy: Allow shim creation based on what's passed to the daemonset
Instead of hardcoding shims as part of the script, let's ensure we can allow them to be created based on environment variables passed to the daemonset. This change brings no functionality change as the default values in the daemonset are exactly what has been used as part of the scripts. Fixes: #7407 Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com> |
||
|
Fabiano Fidêncio
|
8f4b1df9cf |
kata-deploy: Give users the ability to run it on DEBUG mode
The DEBUG env var introduced to the kata-deploy / kata-cleanup yaml file will be responsible for: * Setting up the CRI Engine to run with the debug log level set to debug * The default is usually info * Setting up Kata Containers to enable: * debug logs * debug console * agent logs This will help a lot folks trying to debug Kata Containers while using kata-deploy, and also help us to always run with DEBUG=yes as part of our CI. Fixes: #7342 Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com> |
||
|
Fabiano Fidêncio
|
e8f81ee93d |
Revert "kata-deploy: Use readinessProbe to ensure everything is ready"
This reverts commit
|
||
|
Fabiano Fidêncio
|
5ec9ae0f04 |
kata-deploy: Use readinessProbe to ensure everything is ready
readinessProbe will help us to only have the kata-deploy pod marked as Ready when it finishes all the needed configurations in the node. Related: #6649 Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com> |
||
SinghWang
|
cd2aaeda2a |
kata-deploy: Switch to using an ubuntu image
Let's make sure we use a multi-arch image for building kata-deploy. A few changes were also added in order to get systemd working inside the kata-deploy image, due to the switch from CentOS to Ubuntu. Fixes: #6358 Signed-off-by: SinghWang <wangxin_0611@126.com> |
||
Archana Shinde
|
ee76b398b3 |
release: Revert kata-deploy changes after 3.1.0-rc0 release
As 3.1.0-rc0 has been released, let's switch the kata-deploy / kata-cleanup tags back to "latest", and re-add the kata-deploy-stable and the kata-cleanup-stable files. Signed-off-by: Archana Shinde <archana.m.shinde@intel.com> |
||
|
Archana Shinde
|
d144ded12c |
release: Adapt kata-deploy for 3.1.0-rc0
kata-deploy files must be adapted to a new release. The cases where it happens are when the release goes from -> to: * main -> stable: * kata-deploy-stable / kata-cleanup-stable: are removed * stable -> stable: * kata-deploy / kata-cleanup: bump the release to the new one. There are no changes when doing an alpha release, as the files on the "main" branch always point to the "latest" and "stable" tags. Signed-off-by: Archana Shinde <archana.m.shinde@intel.com> |
||
Peng Tao
|
bf2be0cf7a |
release: Revert kata-deploy changes after 3.0.0-rc0 release
As 3.0.0-rc0 has been released, let's switch the kata-deploy / kata-cleanup tags back to "latest", and re-add the kata-deploy-stable and the kata-cleanup-stable files. Signed-off-by: Peng Tao <bergwolf@hyper.sh> |
||
|
Peng Tao
|
be242a3c3c |
release: Adapt kata-deploy for 3.0.0-rc0
kata-deploy files must be adapted to a new release. The cases where it happens are when the release goes from -> to: * main -> stable: * kata-deploy-stable / kata-cleanup-stable: are removed * stable -> stable: * kata-deploy / kata-cleanup: bump the release to the new one. There are no changes when doing an alpha release, as the files on the "main" branch always point to the "latest" and "stable" tags. Signed-off-by: Peng Tao <bergwolf@hyper.sh> |
||
Fabiano Fidêncio
|
5010c643c4 |
release: Revert kata-deploy changes after 2.5.0-rc0 release
As 2.5.0-rc0 has been released, let's switch the kata-deploy / kata-cleanup tags back to "latest", and re-add the kata-deploy-stable and the kata-cleanup-stable files. Signed-off-by: Fabiano Fidêncio <fabiano@fidencio.org> |
||
|
Fabiano Fidêncio
|
f4eea832a1 |
release: Adapt kata-deploy for 2.5.0-rc0
kata-deploy files must be adapted to a new release. The cases where it happens are when the release goes from -> to: * main -> stable: * kata-deploy-stable / kata-cleanup-stable: are removed * stable -> stable: * kata-deploy / kata-cleanup: bump the release to the new one. There are no changes when doing an alpha release, as the files on the "main" branch always point to the "latest" and "stable" tags. Signed-off-by: Fabiano Fidêncio <fabiano@fidencio.org> |
||
|
Fabiano Fidêncio
|
ccb0183934 |
kata-deploy: Add support to RKE2
"RKE2 - Rancher's Next Generation Kuberentes Distribution" can easily be supported by kata-deploy with some simple adjustments to what we've been relying on for "k3s". The main differences between k3s and RKE2 are, basically: 1. The location where the containerd configuration is stored - k3s: /var/lib/rancher/k3s/agent/etc/containerd/ - rke2: /var/lib/rancher/rke2/agent/etc/containerd/ 2. The name of the systemd services used: - k3s: k3s.service or k3s-agent.service - rke2: rke2-server.service or rke2-agent.service Knowing this, let's add a new overlay for RKE2, adapt the kata-deploy and the kata-cleanup scripts, and that's it. Fixes: #4160 Signed-off-by: Fabiano Fidêncio <fabiano.fidencio@intel.com> |
||
Eric Ernst
|
2b41d275a6 |
release: Revert kata-deploy changes after 2.4.0-rc0 release
As 2.4.0-rc0 has been released, let's switch the kata-deploy / kata-cleanup tags back to "latest", and re-add the kata-deploy-stable and the kata-cleanup-stable files. Signed-off-by: Eric Ernst <eric_ernst@apple.com> |
||
|
Eric Ernst
|
84dff44057 |
release: Adapt kata-deploy for 2.4.0-rc0
kata-deploy files must be adapted to a new release. The cases where it happens are when the release goes from -> to: * main -> stable: * kata-deploy-stable / kata-cleanup-stable: are removed * stable -> stable: * kata-deploy / kata-cleanup: bump the release to the new one. There are no changes when doing an alpha release, as the files on the "main" branch always point to the "latest" and "stable" tags. Signed-off-by: Eric Ernst <eric_ernst@apple.com> |
||
|
Fabiano Fidêncio
|
6955d1442f |
kata-deploy: Add back stable & latest tags
stable-2.3 was the first time we branched the repo since
|
||
|
Peng Tao
|
99c46be787 |
release: Kata Containers 2.3.0-rc0
- runtime# make sure the "Shutdown" trace span have a correct end - tracing: Accept multiple dynamic tags - logging: Enable agent debug output for release builds - agent: "Revert agent: Disable seccomp feature on aarch64 temporarily" - runtime: Enhancement for Makefile - osbuilder: build image-builder image from Fedora 34 - agent: refactor process IO processing - agent-ctl: Update for Hybrid VSOCK - docs: Fix outdated links - ci/install_libseccomp: Fix libseccomp build and misc improvement - virtcontainers: simplify read-only mount handling - runtime: add fast-test to let test exit on error - test: Fix random failure for TestIoCopy - cli: Show available guest protection in env output - Update k8s, critools, and CRI-O to their 1.22 release - package: assign proper value to redefined_string in build-kernel.sh - agent: Make wording of error message match CRI-O test suite - docs: Moving from EOT to EOF - virtcontainers: api: update the functions in the api.md docs - release: Upload libseccomp sources with notice to release page - virtcontainers: check that both initrd and image are not set - agent: Fix the configuration sample file - runtime: set tags for trace span - agent-ctl: Implement Linux OCI spec handling - runtime: Remove comments about unsupported features in config for clh - tools/packaging: Add options for VFIO to guest kernel - agent/runtime: Add seccomp feature - ci: test-kata-deploy: Get rid of slash-command-action action - This is to bump the OOT QAT 1.7 driver version to the latest version.… - forwarder: Drop privileges when using hybrid VSOCK - packaging/static-build: s390x fixes - agent-ctl: improve the oci_to_grpc code - agent: do not return error but print it if task wait failed - virtcontainers: delete duplicated notify in watchHypervisor function - agent: Handle uevent remove actions - enable unit test on arm - rustjail: Consistent coding style of LinuxDevice type - cli: Fix outdated kata-runtime bash completion - Allow VFIO devices to be used as VFIO devices in the container - Expose top level hypervisor methods - - Upgrade to Cloud Hypervisor v19.0 - docs: use-cases: Update Intel SGX use case - virtcontainers: clh: Enable the `seccomp` feature - runtime: delete cri containerd plugin from versions.yaml - docs: Write tracing documentation - runtime: delete useless src/runtime/cli/exit.go - snap: add cloud-hypervisor and experimental kernel - osbuilder: Call detect_rust_version() right before install_rust.sh - docs: Updating Developer Guide re qemu-img - versions: Add libseccomp and gperf version - Enable agent tracing for hybrid VSOCK hypervisors - runtime: optimize test code - runtime: use containerd package instead of cri-containerd - runtime: update sandbox root dir cleanup behavior in rootless hypervisor - utils: kata-manager: Update kata-manager.sh for new containerd config - osbuilder: Re-enable building the agent in Docker - agent: Do not fail when trying to adding existing routes - tracing: Fix typo in "package" tag name - kata-deploy: add .dockerignore file - runtime: change name in config settings back to "kata" - tracing: Remove trace mode and trace type |
||
Fabiano Fidêncio
|
9acf4e5d32 |
kata-deploy: Add stable yaml files
This is **not** the nicest patch of my career, and I know it adds code duplication. However, I've decided to take this approach in order to have easier / better instructions for users who're consuming kata-deploy. Having both stable & latest yaml on `main` will let us point to just one place, without having to update the instructions. I know, would be better to have those generated from a .in file, wouldn't it? For sure, but then we'd lose the ability to just point to those files from kata-deploy pages (either on dockerhub or quay.io). Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> |
||
|
Fabiano Fidêncio
|
a86babe0d0 |
kata-deploy: Point to the latest release
Instead of point to a specific release number, let's point to the `latest` tag on the main branch. There's still some work needed in order to point to the `stable` tag on the stable-x.y branches, as this is something that should be done automagically as part of the release process. Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> |
||
|
Fabiano Fidêncio
|
18c95b9ab1 |
release: Kata Containers 2.3.0-alpha0
- tracing: Change runtime tracing tags to vars - shimv2: add logging to shimv2 api calls - drop qemu-lite support - runtime: delete types or const that no longer needed - runtime: Optimize the way slice created - virtcontainers: simplify tests - virtcontainers: clh: Upgrade to the openapi-generator v5.2.1 - build_image: Fix error soft link about initrd.img - ci: Temporarily skip agent shutdown test on s390x - Fix version parsing for firecracker version 0.25 and over - Osbuilder fixes - docs: update the GoDoc url from runtime project to kata-containers/sr… - docs: update `how-to` README file for Firecracker config - ci/openshift-ci: Pull centos from registry.centos.org - docs: update containerd CRI plugin url |
||
|
Fabiano Fidêncio
|
aaf37d72b2 |
release: Kata Containers 2.2.0-rc0
- use CRI in kata-monitor
- config: Enable jailer by default when using firecracker
- workflows: Actually push the release to quay.io
- docs: update general wording for installation documentation
- Cleanup kernel packaging
- tracing: Return context in runHooks() span creation
- osbuilder: Document no Alpine support on s390x
- osbuilder: Upgrade Ubuntu guest to 20.04
- agent: watcher / inotify stability fixes
- enable snap build for arm64
- agent: Fix cargo 1.54 clippy warning
- osbuilder: Drop Go agent support
- kernel: PTP_KVM support for arm/arm64 in Kata
- docs: update the docs project url from kata 1.x to 2.x
- clh: correct cloud-hypervisor installation on non-x86
- virtcontainers: fc: properly remove jailed block device
- CI: Call agent shutdown test
- kata deploy: always update the base image
- docs: Remove kata-proxy and invalid script reference
- workflows: Actually login to quay.io
- kata-deploy: Update our content to use / point to quay.io/kata-containers rather than katadocker
- agent: Create the process CWD when it does not exist
- Update Kata to allow it to use Qemu 6.1
- osbuilder/dracut: Add missing libraries
- osbuilder: pass env OS_VERSION
- tools: shorten directory path
- virtcontainers: clh: Do not use the default HTTP client
- docs: update kata deploy README doc to add cloud-hypervisor test command
- Container: Add initConfigResourcesMemory and call it in newContainer
- qemu/arm: remove nvdimm/"ReadOnly" option on arm64
- Fix issue container start fail if io.katacontainers.container.resource.swap_in_bytes and memory_limit_in_bytes are not set
- docs: Add tracing proposals doc
- docs: Remove table of contents
- static-checks: Check for the `force-skip-ci` label on each step
- docs: update the kata release url in the kata deploy document
- kata-deploy: Allow build kata-deploy tarball from HEAD
- mod: unify runc and containerd dependencies
- how-to-use-virtio-mem-with-kata.md: Remove undefined ${REPORT_DIR}
- ci: Run static checks when PRs are updated
- docs: update url for log parser in how-to-import-kata-logs-with-fluen…
- versions: Upgrade to Cloud Hypervisor v17.0
- snap: Substitute image configuration with initrd
- docs: Update url for log parser in Developer guide
- mount: fix the issue of missing check file exists
- build(deps): bump github.com/containerd/containerd from 1.5.2 to 1.5.4 in /src/runtime
- docs: Update experimental documentation
- snap: do not export agent version
- Upgrade runc to 1.0.1
- runtime: read-only NVDIMM
- osbuilder/scripts: add support to yq version 4 and above
- osbuilder: update centos arm rootfs image config 'GPG_KEY_ARCH_URL'
- monitor: mv the monitor socket into sbs directory
- fix govet fieldalignment
- docs: added a glossary to support SEO tactics
- ci: expand $CI to nothing
- Add swap support
- snap: fixed snap aarch64 qemu patches dir in snapcraft.yaml file
- agent: clear MsFlags if the option has clear flag set
- snap: Remove QEMU before clone
- docs: fix minikube installation guide runtimeclasses error
- docs: fixed kata-deploy path for kata logs with fluentd doc
- agent/agent-ctl: update tokio to 1.8.1
- ci: set -o nounset
- static-checks: Add a make target to run static-checks locally
- virtiofsd: fix the issue of missing stop virtiofsd
- docs: Update containerd configuration format
- osbuilder: Skip installing golang for building rootfs
- agent-ctl: Use a common Makefile style like other components
- vsock-exporter: switch to tokio runtime
- config: Fix description for OCI hooks
- shimv2: fix the issue of kata-runtime exec failed
|
||
|
Fabiano Fidêncio
|
f47cad3d95 |
tools: Update the image repository to quay.io
This can help our users to **not** hit the pull limitation imposed by dockerhub. Fixes: #2306 Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> |
||
|
Fabiano Fidêncio
|
c8aab29b38 |
release: Kata Containers 2.2.0-alpha1
- runtime: Register defer function at early stage - Ensure the go vendored code is up-to-date and that we actually can call `cargo vendor` on every pull-request - ci: add golang 1.16 to the CI - Update outdated comments and do some minor reworks - snap: Build initrd on ppc64le & s390x - ci: static checks: use defined target_branch - trace-forwarder: Add option rustflags, target, build-type for the make - CI: Honour force-skip-ci label - qemu: stop the virtiofsd specifically - tracing: Consolidate tracing into a new katatrace package - runtime: return error if clh's binary doesn't have a normal stat - osbuilder: Fix the order of checking the distro config directory - agent: Fix to parsing of /proc/self/mountinfo - runtime: Fix lint issues - snap: Miscellaneous s390x fixes - runtime: Use CC=gcc on all RPM-based s390x - s390x: Enable virtio-blk-ccw - forwarder: Add dump only option - shimv2: fix the issue of leaking the hypervisor processes - runtime: Remove the version check for cloud hypervisor - agent: fix wrong regular exp to fetch guest-cid - runtime: refact virtcontainers/pkg/oci - agent: enhance tests of execute_hook - agent: Cleanup config - Pass span context from runtime to agent to get a full trace #1968 - agent: update netlink libraries - shimv2: update containerd vendor - runtime: Format golang proto code - agent: delete some lint attributes - docs: Fix url in virtiofs documentation - tools: agent-ctl: Fix build failure - cargo: Use latest nix crate for all Rust code bases - virtcontainers: Don't fail memory hotplug - Add "watchable-mounts" concept to allow for inotify support of specific types of mounts. - tracing: Make runHooks() span creation return context - kernel: Add Secure Execution guest - packaging: Support Podman in QEMU build - Update qat version - docs: Set LIBC=gnu for s390x too - shimv2: fix the issue of leaking wait goroutines - runtime: report finish time in containers stats - docs: Fix typos in Developer Guide - docs: Update urls for Documentation Requirements document - runtime: update default machine type to q35 - docs: fix brackets usage error for developer guide - Remove the pc machine - runtime: do not hot-remove PMEM devices - docs: Update kata-deploy urls for installation document - docs: Update url for installation guides - agent: Add some mount options and sort the options alphabetically - runtime: using detail propertites instead of function name in log field - qemu: Add nvdimm read-only file support - ci: snap: Fetch history to all branches and tags - memory_offset must be larger than 32 bit - containerd-shim-v2: Skip TestIoCopy unit test - ppc64le: Adding test for appendProtectionDevice - agent: Update rust version for tokio - Upgrade mio to v0.7.13 to fix epoll_fd leak problem - osbuilder: fix log message that is not error but seems like an error - docs: Update url for breaking compatibility - docs: Remove docker support with kata 2.x and sysctls - docs: Update README for runtime documentation - Support SEV - test: Add a unit test for ioCopy() - versions: Upgrade to cloud-hypervisor v16.0 |
||
|
Fabiano Fidêncio
|
54832cd052 |
release: Kata Containers 2.2.0-alpha0
- Update CC=gcc setting for Fedora s390x - osbuilder: Streamline s390x CMake & musl handling - runtime: remove the call to storeSandbox at the end of createSandboxFromConfig - virtcontainers: Add support for Secure Execution - agent: Conform to the latest nix version (0.21.0) - docs: Update the stable branch strategy to what was proposed in our ML - runtime: add more traces for network - tools/packaging: clone meson and dependencies before building QEMU - runtime: remove covertool from cli test - factory: Use lazy unmount - docs: Fix Release Process document - Add sandbox and container ID to trace spans - agent: Fix fd leak caused by netlink - metrics: Add virtiofsd exporter - versions: Update kubernetes to 1.21.1 - tracing: Add basic VSOCK tracing - agent: Upgrade tokio-vsock to fix fd leak of vsock socket - runtime: fix some comments and logs - runtime: Add support for PEF - cleanup TODOs in runtime - tracing: Make runtime span attributes more consistent - virtiofsd: refactor qemu.go to use code in virtiofsd.go - runtime: remove unused doc.go - cgroup: fix the issue of set mem.limit and mem.swap - agent: re-enable the standard SIGPIPE behavior - virtiofsd: Fix file descriptors leak and return correct PID - runtime: and cgroup and SandboxCgroupOnly check for check sub-command - kernel: add ppc64le fragments - docs: Use --ignore-preflight-errors=all flag - agent: fix start container failed when dropping all capabilities - agent: Remove unnecessary underscore(_) variables - docs: Add instructions for getting QEMU source - qemu: align before memory hotplug on arm64 - workflows: release kata 2.x snap through the stable channel - Sandbox bindmount cleanup - docs: Update add customer agent command - agent: Stop relying in the unmaintained prctl crate - how-to-use-virtio-mem-with-kata.md: Update doc to make it clear - docs: Add document for memory hotplug on arm64 - github: Run require porting labels only at main - kernel: add confidential guest build option - rustjail: separated the propagation flags from mount flags - runtime: improve sandbox cleanup logic - docs: add note for connecting debug console for old versions - image_build: align image size to 128M for arm64 - agent: avoid reaping the exit signal of execute_hook in the reaper - agent: move the dependency tempfile to the dev-dependencies section - docs: Document test repository changes when creating a stable branch - docs: Remove horizontal ruler markers that disable spell checks - docs/Developer-Guide: Add instructions to apply QEMU patches - runtime: make dialing timeout configurable - Get sandbox metrics cli - Support TDx - packaging/kata-cleanup: add k3s containerd volume - osbuilder: Upgrade alpine version to 3.13.5 - Monitor cleanup - Open CONFIG_VIRTIO_MEM in x86_64 Linux kernel - agent: delete code which is no longer used - cli: delete tracing code for kata-runtime binary - docs: add per-Pod Kata configurations for `enable_pprof` - Fix issue of virtio-mem - Set fixed NOFILE limit value for kata-agent - ci/install_yq.sh: install_yq: Check version before return - runtime: use s.ctx instead ctx for checking cancellation - runtime: fix some comments |
||
Orestis Lagkas Nikolos
|
9381e5f31a |
packaging/kata-cleanup: add k3s containerd volume
kata-deploy cleanup expects to find containerd configuration in /etc/containerd/config.toml. In case of k3s mount the k3s containerd config as a volume. Fixes #1801 Signed-off-by: Orestis Lagkas Nikolos <olagkasn@nubificus.co.uk> |
||
|
Fabiano Fidêncio
|
799433d863 |
release: Kata Containers 2.1.0-rc0
- Update kata-deploy to use CRI-O drop-in files - Update dependencies versions - fix build kernel shell error when setup with `-f` - virtcontainers: Fix virtio-fs on s390x - Runtimeclass updates - versions: Upgrade to cloud-hypervisor v15.0 - clh: return error if apiSocketPath failed - runtime: fix dropped error - agent: Update seccomp configuration for errnoRet and flags - Fix the issue that sandbox size is not right after update - docs: Document limitation regarding subpaths - qemu: kill virtiofsd if failure to start VMM - runtime/virtcontainers: Fix typo on qmp error msg - cli: delete not used files - runtime: delete not used function parameter builtIn - add io.katacontainers.config.hypervisor.virtio_fs_extra_args handling - Entropy source annotation - runtime: Fix stdout/stderr output from container being truncated - fix the issue of missing set fsGroup for EphemeralStorage - qemu: Fix assertion failure on shutdown - Assorted clippy fixes for Rust agent - agent: use channel instead of pipe(2) to send exit signal of process - Improve agent shutdown handling - Enable virtio-fs on s390x - block: Generate PCI path for virtio-blk devices on clh - runtime: Disable trace for healthcheck - agent/rustjail: Fix accidental damage from tokio conversion - cli: Use genericGetExpectedHostDetails on s390x - runtime/tests: Change "moo FAILURE" message - Update the information about the release process - remove ProcessListContainer API |
||
|
Fabiano Fidêncio
|
4f164b5246 |
release: Kata Containers 2.1.0-alpha2
- release: Do not git add kata-{deploy,cleanup}.yaml for the tests repo
- kata-deploy: add runtimeclass that includes pod overhead
- release: automatically bump the version of the kata-deploy images
- Refine uevent matching conditions
- docs: update dev-guide to include fixes from 1.x
- virtcontainers: replace newStore by store in Sandbox struct
- agent: log the mount point if it is already mounted
- tools/agent-ctl: Update Cargo.lock
- agent: Rework the debug console
- oci: Update seccomp configuration
- kernel: update experimental kernel to 5.10.x
- kata-deploy: Fix `test-kata.sh` and do some small cleanups / improvements in the kata-deploy script
- github: Fix slash-command-action usage
- rustjail: fix the issue of missing default home env
- Make uevent watching mechanism more flexible
- ci/openshift-ci: Prepare to build on CentOS 8
- docs: update configuration for passing annotations in conatinerd
- Revert "github: Remove kata-deploy-test action"
- runtime: increase dial timeout
- qemu experimental: Move to latest tree on virtio-fs-dev (qemu 6.0 + DAX patches).
- github: Remove kata-deploy-test action
- agent: s390x statfs constants
- kernel: upgrade kernel to 5.10.x for arm64.
- Don't do anything in Pipestream::shutdown
- Fix fsgroup
- agent: Remove many "panic message is not string literal" warnings
- osbuilder: Update QAT Dockerfile with new QAT driver version
- osbuilder: update dockerfiles to utilize IMAGE_REGISTRY
- Only keep one VERSION file
- Dechat deruntime
- runtime: Format auto-generated client code for cloud-hypervisor API
- runtime: use concrete KataAgentConfig instead of interface type
- versions: Update cloud-hypervisor to release v0.14.1
- runtime: import runtime/v2/runc/options to decode request from Docker
- virtcontainers/fc: Upgrade Firecracker to v0.23.1
- docs: Remove ubuntu installation guide
- docs: Update snap install guide
- docs: update how-to-use-k8s-with-cri-containerd-and-kata.md
- Update install docs for Fedora and CentOS
- action: fix missing qemu tag
- Remove installation guides for SLE and openSUSE
- kernel: Enable OVERLAY_FS_{METACOPY,XINO_AUTO}
- versions: kernel 5.10.x
- virtcontainers: Fix missing contexts in s390x
- runtime: makefile allow override DAX value
|
||
|
Fabiano Fidêncio
|
f444adb51b |
kata-cleanup: Explicitly add tag to the container image
We have the tags explicitly set on kata-deploy, let's do the same for kata-cleanup. Signed-off-by: Fabiano Fidêncio <fidencio@redhat.com> |
||
|
Peng Tao
|
782cd2ed10 |
packaging: merge packaging repository
git-subtree-dir: tools/packaging git-subtree-mainline: |