From 98bacb0efce7296609e7ffbebbcfeae1bdab9171 Mon Sep 17 00:00:00 2001 From: Archana Shinde Date: Tue, 14 Feb 2023 15:44:20 -0800 Subject: [PATCH 1/2] release: Adapt kata-deploy for 3.0.2 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 --- tools/packaging/kata-deploy/kata-cleanup/base/kata-cleanup.yaml | 2 +- tools/packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/tools/packaging/kata-deploy/kata-cleanup/base/kata-cleanup.yaml b/tools/packaging/kata-deploy/kata-cleanup/base/kata-cleanup.yaml index 90f2c698c8..110d0133af 100644 --- a/tools/packaging/kata-deploy/kata-cleanup/base/kata-cleanup.yaml +++ b/tools/packaging/kata-deploy/kata-cleanup/base/kata-cleanup.yaml @@ -18,7 +18,7 @@ spec: katacontainers.io/kata-runtime: cleanup containers: - name: kube-kata-cleanup - image: quay.io/kata-containers/kata-deploy:3.0.1 + image: quay.io/kata-containers/kata-deploy:3.0.2 imagePullPolicy: Always command: [ "bash", "-c", "/opt/kata-artifacts/scripts/kata-deploy.sh reset" ] env: diff --git a/tools/packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml b/tools/packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml index 408de3e248..4dbc29d7e3 100644 --- a/tools/packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml +++ b/tools/packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml @@ -16,7 +16,7 @@ spec: serviceAccountName: kata-label-node containers: - name: kube-kata - image: quay.io/kata-containers/kata-deploy:3.0.1 + image: quay.io/kata-containers/kata-deploy:3.0.2 imagePullPolicy: Always lifecycle: preStop: From 2f638b366605c20be9c1fa934bc147ebcf2e35b7 Mon Sep 17 00:00:00 2001 From: Archana Shinde Date: Tue, 14 Feb 2023 15:44:20 -0800 Subject: [PATCH 2/2] release: Kata Containers 3.0.2 - stable-3.0: Stable 3.0 backports - stable-3.0 | docs: Fix missing critical steps in how-to-hotplug-memory-arm64.md - Stable-3.0 | Upgrade to Cloud Hypervisor v28.2 - Qemu logs for stable 3.0 - Backport CI fixes for s390x and ppc64le to stable-3.0 - docs: Fix missing critical steps in how-to-hotplug-memory-arm64.md - Stable-3.0 | Upgrade to Cloud Hypervisor v28.1 4ebeb51bb release: Adapt kata-deploy for 3.0.2 178ee3d7e agent: check command before do test_ip_tables 7461bcd76 runtime-rs: change cache mode 123c86717 SEV: Update ReducedPhysBits 98f60c100 clh: Enforce API timeout only for vm.boot request 960f089d3 virtiofsd: fix the build on ppc64le 92f3b11c9 runtime:all APIs are hang in the service.mu 92619c833 runtime: Drop QEMU log file support 4f3db7678 runtime: Collect QEMU's stderr 918c11e46 runtime: Start QEMU undaemonized 8c4507be2 runtime: Launch QEMU with cmd.Start() a61fba6d4 runtime: Pre-establish the QMP connection ad9cb0ba5 govmm: Optionally pass QMP listener to QEMU d6dd99e98 govmm: Optionally start QMP with a pre-configured connection 0623f1fe6 virtiofsd: Not use "link-self-contained=yes" on s390x 5883dc1bd CI: Set docker version to v20.10 in ubuntu:20.04 for s390x|ppc64le 4a5877f45 docs: Fix missing critical steps in how-to-hotplug-memory-arm64.md d3b57325e versions: Upgrade to Cloud Hypervisor v28.2 0d7bd066d docs: Fix missing critical steps in how-to-hotplug-memory-arm64.md ac1ce2d30 docs: Fix missing critical steps in how-to-hotplug-memory-arm64.md f4d71af45 docs: Fix missing critical steps in how-to-hotplug-memory-arm64.md fcc120d49 versions: Upgrade to Cloud Hypervisor v28.1 Signed-off-by: Archana Shinde --- VERSION | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/VERSION b/VERSION index cb2b00e4f7..b502146930 100644 --- a/VERSION +++ b/VERSION @@ -1 +1 @@ -3.0.1 +3.0.2