From 84b94dc2b14de74813a937d6d35a00cf70a8b55a Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Wed, 8 May 2024 13:35:48 +0200 Subject: [PATCH] kata-deploy: Expose /host to the daemon-set MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit We'll need to have access to the host os-release file (either under `/etc/os-release` or under `/usr/lib/os-release`), and the simplest approach that comes to my mind to do is doing what a debug pod would do, mounting `/` as `/host` and then allowing us to have access to those files, and then corectly set the TDX specific QEMU and OVMF (TDVF) paths for the tdx available configurations. Signed-off-by: Fabiano Fidêncio --- .../packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml | 5 +++++ 1 file changed, 5 insertions(+) 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 5e17214e50..1d552e4d84 100644 --- a/tools/packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml +++ b/tools/packaging/kata-deploy/kata-deploy/base/kata-deploy.yaml @@ -58,6 +58,8 @@ spec: mountPath: /opt/kata/ - name: local-bin mountPath: /usr/local/bin/ + - name: host + mountPath: /host/ volumes: - name: crio-conf hostPath: @@ -72,6 +74,9 @@ spec: - name: local-bin hostPath: path: /usr/local/bin/ + - name: host + hostPath: + path: / updateStrategy: rollingUpdate: maxUnavailable: 1