github/confidential-containers
1
0
Fork 0
mirror of https://github.com/confidential-containers/confidential-containers.git synced 2025-10-21 15:31:13 +00:00
Code Issues Packages Projects Releases Wiki Activity

quickstart: Update the required vCPU numbers to 4

Browse Source 
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 <fabiano.fidencio@intel.com>
This commit is contained in:
Fabiano Fidêncio
2023-01-17 13:14:39 +01:00
committed by Fabiano Fidêncio
parent fdf5f4b2d2
commit 9faf24a7f2
1 changed files with 1 additions and 1 deletions
Download Patch File Download Diff File Expand all files Collapse all files

2
quickstart.md
View File

@@ -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=`