Accounting for the number of served cluster nodes when scaling
One instance of Kaspersky Container Security supports working with up to 600 monitored clusters. The number of served nodes of each cluster is scaled by changing the following components:
kcs-ab to increase or reduce the number of component replicas.
kcs-memcached to increase or reduce the resource allocation requirements of the component.
By default, Kaspersky Container Security is shipped with the following values set for these components:
kcs-ab:
1 pod per replica allowing to serve 2000 nodes.
Requested amount of resources: 0.5 CPU core for nodes; 512 MB of RAM for nodes.
Maximum resource usage: 1 CPU core for nodes; 1 GB of RAM for nodes.
kcs-memcached:
Requested amount of resources: 2 CPU core for nodes; 2 GB of RAM for nodes.
Maximum resource usage: 4 CPU core for nodes; 4 GB of RAM for nodes.
Kaspersky Container Security scales by increasing the following parameters:
For kcs-ab, adding one pod to a replica increases the number of supported nodes by 2000.
For kcs-memcached, adding one pod to the kcs-ab component requires increasing the requested resources and the maximum resource usage of the kcs-memcached component by the following amounts:
Requested amount of resources: 0.5 CPU core for nodes; 2 GB of RAM for nodes.
Maximum resource usage: 0.5 CPU core for nodes; 2 GB of RAM for nodes.
For example, if an instance of Kaspersky Container Security serves 10,000 nodes in a user's clusters, the following parameters apply:
kcs-ab:
5 pods per replica.
Requested amount of resources: 0.5 CPU core per node; 512 MB of RAM per node.
Maximum resource usage: 1 CPU core for nodes; 1 GB of RAM for nodes.
kcs-memcached:
Requested amount of resources: 4 CPU core for nodes; 10 GB of RAM for nodes.
Maximum resource usage: 6 CPU core for nodes; 12 GB of RAM for nodes.
The values given are approximate because the deployment requires taking into account the specifics of virtualization settings and the performance of host servers (nodes) in the given infrastructure.