You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@homergleason Remove those, we maintain a fork pending fixes related to Hetzner are shipped in a future version. So just delete those lines to use our own fork:
Then just make sure to give it enough load, with such powerful nodes, you may need to give way bigger ressource requests than in the example below:
apiVersion: apps/v1kind: Deploymentmetadata:
name: force-scale-upspec:
replicas: 1selector:
matchLabels:
app: force-scale-uptemplate:
metadata:
labels:
app: force-scale-upspec:
containers:
- name: busyboximage: busyboxargs:
- /bin/sh
- -c
- "while true; do echo 'Forcing scale up...'; sleep 60; done"resources:
requests:
cpu: 2000m# Requesting a high amount of CPU to force scale upmemory: 4Gi # Requesting a high amount of memory to force scale up
Description
Hello, I’ve been struggling all day, I just can’t start autoscaling.
Set node group draining-node-pool size from 0 to 0, expected delta 0
Although the configuration says something completely different.
Kube.tf file
Screenshots
No response
Platform
Linux
The text was updated successfully, but these errors were encountered: