Question
pod didn't trigger scale-up (it wouldn't fit if a new node is added)
Autoscaling worked fine (kubernetes added new 1cpu/2gbRAM droplet/node to cluster automatically) when i started a kubernetes Job with
requested memory: "800Mi", parallelism: 2
but when i tried to start a job with requested memmory: "2000Mi, parallelism: 2
it showing error in job’s event logs
pod didn't trigger scale-up (it wouldn't fit if a new node is added): 1 Insufficient memory
kubectl apply -f job.yaml
apiVersion: batch/v1
kind: Job
metadata:
name: scaling-test
spec:
parallelism: 2
template:
metadata:
name: scaling-test
spec:
containers:
- name: debian
image: debian
command: ["/bin/sh","-c"]
args: ["sleep 300"]
resources:
requests:
cpu: "100m"
memory: "1900Mi"
restartPolicy: Never
My assumption was, kubernetes while autoscaling will add new node with respect to job’s requested resource requirements.(add 1cpu/3gbRAM node) any idea how to make kubernetes autoscale and provision a node based on job’s requested resources?
These answers are provided by our Community. If you find them useful, show some love by clicking the heart. If you run into issues leave a comment, or add your own answer to help others.
×