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
{{ message }}
This repository has been archived by the owner on Nov 1, 2021. It is now read-only.
Why does this not work with statefulsets? I editted autoscale.sh to "statefulsets" instead of "deployments" but it doesn't seem to work, even though the command work outside of autoscale.sh
I simple keep getting:
Fri May 31 14:33:49 UTC 2019 -- Failed to get current pods number for [statefulset-name]
The text was updated successfully, but these errors were encountered:
The reason you're getting "Failed to get current pods number for [statefulset-name]" is because deployment is currently hardcoded, and your cluster doesn't have [statefulset-name] deployment
You could easily adapt this script by finding all kubectl commands that currently manipulate deployment, and replace deployment with statefulset.
I had a brief look and think that kubectl describe statefulset and kubectl scale statefulset should both work out of the box.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Why does this not work with statefulsets? I editted autoscale.sh to "statefulsets" instead of "deployments" but it doesn't seem to work, even though the command work outside of autoscale.sh
I simple keep getting:
Fri May 31 14:33:49 UTC 2019 -- Failed to get current pods number for [statefulset-name]
The text was updated successfully, but these errors were encountered: