mirror of
https://github.com/kubernetes-sigs/descheduler.git
synced 2026-01-26 05:14:13 +01:00
a3f8bb0369
Prior to this commit the YAML manifests used to install the descheduler Job and CronJob did not set container requests or limits. This is considered an anti-pattern when deploying applications on k8s. Set descheduler container resources to make it a burstable pod. This will ensure a high quality experience for end users when deploying descheduler into their clusters using the instructions from the README. The values choosen for CPU/Memory are not based on any real data.
38 lines
903 B
YAML
38 lines
903 B
YAML
---
|
|
apiVersion: batch/v1
|
|
kind: Job
|
|
metadata:
|
|
name: descheduler-job
|
|
namespace: kube-system
|
|
spec:
|
|
parallelism: 1
|
|
completions: 1
|
|
template:
|
|
metadata:
|
|
name: descheduler-pod
|
|
spec:
|
|
priorityClassName: system-cluster-critical
|
|
containers:
|
|
- name: descheduler
|
|
image: k8s.gcr.io/descheduler/descheduler:v0.19.0
|
|
volumeMounts:
|
|
- mountPath: /policy-dir
|
|
name: policy-volume
|
|
command:
|
|
- "/bin/descheduler"
|
|
args:
|
|
- "--policy-config-file"
|
|
- "/policy-dir/policy.yaml"
|
|
- "--v"
|
|
- "3"
|
|
resources:
|
|
requests:
|
|
cpu: "500m"
|
|
memory: "256Mi"
|
|
restartPolicy: "Never"
|
|
serviceAccountName: descheduler-sa
|
|
volumes:
|
|
- name: policy-volume
|
|
configMap:
|
|
name: descheduler-policy-configmap
|