Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

docs: installation: scaling: mention kubernetes core components resou… #1295

Open
wants to merge 2 commits into
base: main
Choose a base branch
from
Open

docs: installation: scaling: mention kubernetes core components resou… #1295

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
c5768be
docs: installation: scaling: mention kubernetes core components resou…
Jun 20, 2024
20e4403
Merge branch 'main' into main
JimBugwadia Oct 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions content/en/docs/installation/scaling.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -81,3 +81,10 @@ API requests, operations, and activities which match corresponding Kyverno rules
| DELETE | ConfigMap | | 1 |

These figures were captured using K3d v5.4.9 on Kubernetes v1.26.2 and Kyverno 1.10.0-alpha.2 with a 3-replica admission controller. When testing against KinD, there may be one less DELETE AdmissionReview for Pod-related operations.

### Kubernetes api-server and etcd resource footprint

In clusters with many Kyverno policy resources, the resource footprint of some core Kubernetes components may be affected, in particular the kube-apiserver and etcd.

For example, if you create several thousand Kyverno policy resources, double check that the kube-apiserver pods have head room to increase its memory allocations, otherwise
the cluster may crash entirely.