docs: installation: scaling: mention kubernetes core components resou… #1295
Conversation
…rces footprint Introduce a mention to how many kyverno resources may impact the kubernetes core components regarding their resources footprint. See also: kyverno/kyverno#10458 Signed-off-by: Arturo Borrero Gonzalez <[email protected]>
|
Thanks for opening your first Pull Request here! Please check out our Contributing guidelines and confirm that you Signed off. |
|
Hi @chipzoller - can you help review? |
The idea is to prevent folks from having to reach to the troubleshooting section. I added to the scaling section because I liked the idea of having everything related to the topic of how to operate kyverno at scale on the same page. Should I have this information here when I started working with kyverno, would have saved me quite a few hours of work. |
|
But this is a really, really niche concern. Prior to you, we had never heard of people using truly "thousands" of Kyverno policies let alone the problems they might cause. |
The troubleshooting section is "after the fact" documentation. I expect anything related to kubernetes ecosystem to be extremely scalable by default. Ideally, handling a few thousand resources would be no big deal for kyverno. If handling such a load is not big deal, then it should be clearly documented. But not hidden as an "after the fact" information. It should be front and center, and in that sense, I can't think of a reason why a section called "scalability" would be the wrong place to put this information. |
Congratulations! 🎉Great job merging your first Pull Request here! How awesome! If you are new to this project, feel free to join our Slack community.
|
…rces footprint
Introduce a mention to how many kyverno resources may impact the kubernetes core components regarding their resources footprint.
See also: kyverno/kyverno#10458
Related issue
Proposed Changes
Checklist