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
Now when I change scaleDownEnabled: false, the deployment is stuck in updating state
NAME READY ATLAS STATE MONGODB VERSION
data-vault False UPDATING 8.0.4
And when I describe
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Normal DeploymentUpdating 4m47s (x3600 over 32d) AtlasDeployment deployment is updating
What did you expect?
Deployment should have been updated successfully
What happened instead?
Deployment is stuck in a loop
Operator Information
2.6.0
The text was updated successfully, but these errors were encountered:
This is definitely a bug. To disable autoscaling I had to remove the autoscaling block from the spec entirely and I had to look at the source code to comprehend this.
P.S the autoscaling actually gets disabled when I set autoscaling.enabled = false but the deployment never becomes ready
Thank you, again, for bringing this issue to our attention. Our team has successfully reproduced the error, and we can confirm it is a bug. As a temporary workaround, you can remove autoscaling configuration and add it back once the cluster is idle, as you have already discovered. Our team is actively investigating a more permanent solution by assessing the possibility of removing the validation constraints around autoscaling without impacting the usability of the resource. Please note that developing and testing a proper fix might take some time. We appreciate your patience and will keep you updated on our progress.
What did you do to encounter the bug?
Steps to reproduce the behavior:
I have a deployment with autoscaling enabled
Now when I change
scaleDownEnabled: false
, the deployment is stuck in updating stateAnd when I describe
What did you expect?
Deployment should have been updated successfully
What happened instead?
Deployment is stuck in a loop
Operator Information
The text was updated successfully, but these errors were encountered: