Skip to content
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

Wait for available AKS resources (Okteto CLI) #1622

Closed
pnol opened this issue Jun 22, 2021 · 1 comment · Fixed by #1645
Closed

Wait for available AKS resources (Okteto CLI) #1622

pnol opened this issue Jun 22, 2021 · 1 comment · Fixed by #1645
Assignees

Comments

@pnol
Copy link

pnol commented Jun 22, 2021

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.

@pchico83
Copy link
Contributor

Thanks for this issue @pnol, I think we can have an extended notation like:

timeout:
   default: 30
   resources: 300

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants