New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Autoscaling size below current size and PVC size not human readable. #3
Comments
@GuillaumeOuint Can you enable verbose mode? It'll print out a LOT more data, and hopefully you can gist or pastebin or something the verbose dump of the failure. If you're worried about issues arising please enable dry-run mode also. For reference to enable those either set the values in your helm values file, or use the CLI args when installing the helm chart. See: https://github.com/DevOps-Nirvana/Kubernetes-Volume-Autoscaler/#installation-with-helm Also, could you please provide all the other custom (non-default) values you've set in this helm chart? Thanks! |
@AndrewFarley I've manually resized the PVCs so I have to wait some days for a new trigger. For the helm chart config, I've just edited slack webhook, channel, prometheus URL and: scale_above_percent: "80"
scale_after_intervals: "5"
scale_cooldown_time: "22200"
scale_up_max_increment: "2000000000"
scale_up_max_size: "20000000000"
scale_up_min_increment: "1000000000"
scale_up_percent: "10" |
@GuillaumeOuint Alright, yeah all your settings look good nothing funny. I'm eager to hear what verbose mode shows. Even now for the
Those raw values above are what I need. Thanks! |
Also, I would ask what is the provisioner @GuillaumeOuint? Please get the yaml of the storageclass you're using and dump it here for me. Thanks! |
Hi @AndrewFarley, here is the verbose output for infra.data-nfs-server-provisioner-1637948923-0:
I use scaleway as provider, here is the storage class: apiVersion: storage.k8s.io/v1
kind: StorageClass
metadata:
name: scw-bssd
labels:
k8s.scw.cloud/object: StorageClass
k8s.scw.cloud/system: csi
provisioner: csi.scaleway.com
reclaimPolicy: Delete
allowVolumeExpansion: true
volumeBindingMode: Immediate |
@GuillaumeOuint I see the flaw. The problem is that you've set the To fix: Remove your overriding of the value: Cheers! |
@AndrewFarley Oh snap, I didn't realize this typo error on my side, sorry. |
@GuillaumeOuint Sounds like a great feature, I'll make them human readable. Thanks for the idea! |
About to release 1.0.5, with verbose details which shows exactly what the values are in the logs, and it would catch that error you ran into in the logs.
|
Sometimes, the autoscaler tries to resize a PVC with a size below current size, raising an error.
I'm using the helm chart version 1.0.3 (same image tag)
Another issue, the autoscaler was able to resize another PVC from 13Gi to 14173392076, this is not human readable as before. It's not a serious issue but it's still disturbing. The autoscaler also sent the alert to slack twice for this PVC with several hours interval.
The text was updated successfully, but these errors were encountered: