Configure Resource Limits

Determining resource limits is a process that should take place after the initial setup of your cluster. This is especially true for proof-of-concept clusters. Once you have configured your cluster to accommodate a critical mass of data, tune the resource limits for your Fusion services.

In the case of production or production-like environments, define resource limits to help Kubernetes schedule pods correctly across the nodes in your cluster. This is important for Kubernetes clusters that host namespaces other than Fusion.

If you used the --with-resource-limits option when running the ./customize_fusion_values.sh script, resource limits are already configured for your cluster. The script creates a YAML file for this purpose named <provider>_<cluster>_<namespace>_fusion_resources.yaml. Alternatively, you can copy resources.yaml, and rename it using the following naming convention: <provider>_<cluster>_<release>_fusion_resources.yaml.

You can refine the resource requests and limits as you test your cluster’s behavior, while preparing for a production environment with Fusion.