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
Is your feature request related to a problem? Please describe.
When there are no sufficient resources available in AKS and I run Okteto up, the deployment fails with an "insufficient resources" error. In the meantime k8s/aks figured out it needs to scale out and additional nodes are provisioned. After about 4 minutes an extra node is ready and the Okteto deployment (was still trying to deploy) succeeds. However the Okteto cli already backed off with an error.
Describe the solution you'd like
A similar option as timeout would be great where we can specify the amount of minutes a deployment can wait or "look" for available resources.
example:
resource_timeout: 6m
When this option is used, instead of an immediate error it would be nice to see an info/warning message saying it's will look for resources for $resource_timeout more minutes.
Describe alternatives you've considered
Two alternatives considered: running Okteto up again after a couple of minutes and see if it works then, or running more default resources which means overpaying on nodesmost of the time.
The text was updated successfully, but these errors were encountered:
I'm using the Okteto CLI in combination with AKS.
Is your feature request related to a problem? Please describe.
When there are no sufficient resources available in AKS and I run Okteto up, the deployment fails with an "insufficient resources" error. In the meantime k8s/aks figured out it needs to scale out and additional nodes are provisioned. After about 4 minutes an extra node is ready and the Okteto deployment (was still trying to deploy) succeeds. However the Okteto cli already backed off with an error.
Describe the solution you'd like
A similar option as timeout would be great where we can specify the amount of minutes a deployment can wait or "look" for available resources.
example:
resource_timeout: 6m
When this option is used, instead of an immediate error it would be nice to see an info/warning message saying it's will look for resources for $resource_timeout more minutes.
Describe alternatives you've considered
Two alternatives considered: running Okteto up again after a couple of minutes and see if it works then, or running more default resources which means overpaying on nodesmost of the time.
The text was updated successfully, but these errors were encountered: