This topic describes the resources required to install and use Services Toolkit.
Note: At present it is not possible to alter default resource configurations for Services Toolkit as part of installation.
To better understand resource requirements and use, consider the various Kubernetes deployments that are created as part of installation, and subsequent use of Services Toolkit.
Upon installation of Services Toolkit to a cluster, a single Deployment named services-toolkit-controller-manager
is created and it defines a container with the following resource configuration:
resources:
limits:
cpu: 200m
memory: 500Mi
requests:
cpu: 100m
memory: 100Mi
Note: See the Kubernetes documentation for further information about resource management in Kubernetes.
For each DownstreamClusterLink
resource created as part of configuring a Projection Plane (see Service API Projection and Service Resource Replication), one additional Deployment
is created on the downstream cluster. This Deployment
defines a container with the following resource configuration:
resources:
limits:
cpu: 100m
memory: 100Mi
requests:
cpu: 100m
memory: 20Mi
There is one additional Deployment
for each ClusterResourceExportMonitor
and ClusterResourceImportMonitor
resource that is created upon configuration of Resource Replication (see Service API Projection and Service Resource Replication). This Deployment
defines a container with the following resource configuration:
resources:
limits:
cpu: 100m
memory: 100Mi
requests:
cpu: 100m
memory: 20Mi
Therefore, the minimum set of resources required to support the federation of an API between a Workload Cluster and a Service Cluster is as follows:
Workload Cluster
Service Cluster
Total minimum resource requirements
Note: Services Toolkit does not require the use of volumes or any external storage.