# Cluster Resource Limits
Entando needs a well-defined amount of resources in order to start and Kubernetes takes care of using only the needed amount of them.
However, you can choose to impose boundaries on the minimum and maximum used/allocated resources by updating the downloaded
entando.yaml file and setting the
ENTANDO_K8S_OPERATOR_IMPOSE_DEFAULT_LIMITS property to true.
In this way, Entando will allocate a predefined amount of resources and Kubernetes will act more strictly checking for resource availability. See Kubernetes resources (opens new window) for more information.
By not imposing limits you can minimize initial needed resources and startup time, leaving Kubernetes free to manage its resources as he wants. By imposing limits you can obtain a better-balanced system.
It's important to note that, accordingly to the Kubernetes documentation, in order to deploy on a namespace with a ResourceQuotas (opens new window) on memory and cpu,
every Container must have a memory request, memory limit, cpu request, and cpu limit
so, in that case, you will need to set
ENTANDO_K8S_OPERATOR_IMPOSE_DEFAULT_LIMITS to true, otherwise your deploy will fail.
Here you can see the detailed resource requests/limits per container:
|Component||Mem requests||CPU requests||Mem limits||CPU limits|
# Bundle size limitations
Entando supports bundles without size limitations, you can install as many bundles as you want and bundles as big as you desire.
The only thing you have to check is the
<YOUR-APP-NAME>-de-pvc volume size. Each bundle is installed in that volume, so when it reaches its maximum capacity you will not be able to install bundles anymore.
You can find
quickstart-de-pvc volume inside de-container container, that is part of the pod named
<YOUR-APP-NAME>-server-deployment-***, where asterisks should assume values based on your instance.
Feel free to set its size accordingly to your needs.