From 3bdcfaa6583025c4d37521d0e681827e886f1ff3 Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Tue, 21 Sep 2021 22:18:12 +0200 Subject: [PATCH] kata-deploy: Add more info about the stable tag MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit Let's make it as clear as possible for the user that if they go for a tagged version of kata-deploy, eg, 2.2.1, they'll have the kata runtime 2.2.1 deployed on their cluster. Suggested-by: Eric Adams Signed-off-by: Fabiano FidĂȘncio --- tools/packaging/kata-deploy/README.md | 3 +++ 1 file changed, 3 insertions(+) diff --git a/tools/packaging/kata-deploy/README.md b/tools/packaging/kata-deploy/README.md index cff1a831a1..9f54f0a728 100644 --- a/tools/packaging/kata-deploy/README.md +++ b/tools/packaging/kata-deploy/README.md @@ -24,6 +24,9 @@ $ kubectl apply -f https://raw.githubusercontent.com/kata-containers/kata-contai The stable image refers to the last stable releases content. +Note that if you use a tagged version of the repo, the stable image does match that version. +For instance, if you use the 2.2.1 tagged version of the kata-deploy.yaml file, then the version 2.2.1 of the kata runtime will be deployed. + ```sh $ kubectl apply -f https://raw.githubusercontent.com/kata-containers/kata-containers/main/tools/packaging/kata-deploy/kata-rbac/base/kata-rbac.yaml $ kubectl apply -f https://raw.githubusercontent.com/kata-containers/kata-containers/main/tools/packaging/kata-deploy/kata-deploy/base/kata-deploy-stable.yaml