Files
weave-scope/examples/k8s/deploy.yaml
Bryan Boreham b739a5ce5e 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.
2019-02-13 17:56:59 +00:00

40 lines
915 B
YAML

# borrowed from https://cloud.weave.works/k8s/scope.yaml?k8s-version=1.9.3
apiVersion: apps/v1
kind: Deployment
metadata:
name: weave-scope-app
labels:
name: weave-scope-app
app: weave-scope
weave-cloud-component: scope
weave-scope-component: app
namespace: weave
spec:
replicas: 1
selector:
matchLabels:
app: weave-scope
revisionHistoryLimit: 2
template:
metadata:
labels:
name: weave-scope-app
app: weave-scope
weave-cloud-component: scope
weave-scope-component: app
spec:
containers:
- name: app
args:
- '--no-probe'
env: []
image: weaveworks/scope:1.10.2
imagePullPolicy: IfNotPresent
ports:
- containerPort: 4040
protocol: TCP
resources:
requests:
cpu: 200m
memory: 200Mi