Recommended settings for monitoring and collecting metrics for Kubernetes, platform services, and applications deployed on the cluster

D2iQ conducts routine performance testing of Kommander. The following table provides recommended settings, based on cluster size and increasing workloads, that maintain a healthy Prometheus monitoring deployment.

The resource settings reflect some settings but do not represent the exact structure to be used in the platform service configuration.

Prometheus

Cluster Size

Number of Pods

Number of Services

Resource settings

10

1k

250

resources:
  limits:
    cpu: 500m
    memory: 2192Mi
  requests:
    cpu: 100m
    memory: 500Mi
storage: 35Gi
CODE

25

1k

250

resources:
  limits:
    cpu: 2
    memory: 6Gi
  requests:
    cpu: 1
    memory: 3Gi
storage: 60Gi
CODE

50

1.5k

500

resources:
  limits:
    cpu: 7
    memory: 28Gi
  requests:
    cpu: 2
    memory: 8Gi
storage: 100Gi
CODE

100

3k

1k

resources:
  limits:
    cpu: 12
    memory: 50Gi
  requests:
    cpu: 10
    memory: 48Gi
storage: 100Gi
CODE

200

10k

3k

resources:
  limits:
    cpu: 20
    memory: 80Gi
  requests:
    cpu: 15
    memory: 50Gi
storage: 100Gi
CODE

300

15k

6k

resources:
  limits:
    cpu: 35
    memory: 150Gi
  requests:
    cpu: 25
    memory: 120Gi
storage: 100Gi
CODE