From 9faf24a7f26053820bd0c8a809134b2e8ed52d2d Mon Sep 17 00:00:00 2001 From: =?UTF-8?q?Fabiano=20Fid=C3=AAncio?= Date: Tue, 17 Jan 2023 13:14:39 +0100 Subject: [PATCH] quickstart: Update the required vCPU numbers to 4 MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit While preparing the `v0.3.0` release, we've noticed that using a VM with 2 vCPUs would lead to: ``` Name: cc-operator-controller-manager-79797456f6-spmss Namespace: confidential-containers-system ... Events: Type Reason Age From Message ---- ------ ---- ---- ------- Warning FailedScheduling 4m12s default-scheduler 0/1 nodes are available: 1 Insufficient cpu. preemption: 0/1 nodes are available: 1 No preemption victims found for incoming pod. ``` And this is *NOT* something introduced between `v0.2.0` and `v0.3.0`, as it also happen with the previous release. For now, let's update the documentation accordingly and revisit this after the release in case we need to really rely on deploying in nodes with 2 vCPUs. Signed-off-by: Fabiano Fidêncio --- quickstart.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/quickstart.md b/quickstart.md index 8206934..fc8b7a4 100644 --- a/quickstart.md +++ b/quickstart.md @@ -42,7 +42,7 @@ on the worker nodes is **not** on an overlayfs mount but the path is a `hostPath ## Prerequisites -- Ensure a minimum of 8GB RAM and 2 vCPU for the Kubernetes cluster node +- Ensure a minimum of 8GB RAM and 4 vCPU for the Kubernetes cluster node - Only containerd runtime based Kubernetes clusters are supported with the current CoCo release - The minimum Kubernetes version should be 1.24 - Ensure at least one Kubernetes node in the cluster is having the label `node-role.kubernetes.io/worker=`