Add CPU and memory requests to example Kubernetes manifests

If you don't specify, the default is typically 0 which (a) gives the
Kubernetes scheduler a false idea of expected usage and (b) makes the
Linux scheduler penalise the Scope processes under contention.

For best results adjust the figures here after observing actual usage
on your cluster.
This commit is contained in:
Bryan Boreham
2019-02-13 17:56:59 +00:00
parent c0b2690679
commit b739a5ce5e
2 changed files with 8 additions and 0 deletions

View File

@@ -33,3 +33,7 @@ spec:
ports:
- containerPort: 4040
protocol: TCP
resources:
requests:
cpu: 200m
memory: 200Mi

View File

@@ -38,6 +38,10 @@ spec:
fieldPath: spec.nodeName
image: weaveworks/scope:1.10.2
imagePullPolicy: IfNotPresent
resources:
requests:
cpu: 100m
memory: 100Mi
securityContext:
privileged: true
volumeMounts: