We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
When we try to create a new MD for a usercluster with provider = Azure, the VM list loading takes really long time. Almost 3 minutes!!
We should ideally pre-cache this list for really long time and also update this cached entry in background so that user experience is always smooth.
Some screenshots.
VM sizes dropdown should be ready in less than 5 seconds
Try to create a user-cluster with Azure as the provider. On the screen to add Machine deployment - observe the time taken to populate VM sizes.
No workaround. I wait for 3 minutes to populate the list.
kubermatic/machine-controller#1857 might be also using same API in the background and times out continuously
The text was updated successfully, but these errors were encountered:
/milestone KKP 2.27
Sorry, something went wrong.
No branches or pull requests
What happened
When we try to create a new MD for a usercluster with provider = Azure, the VM list loading takes really long time. Almost 3 minutes!!
We should ideally pre-cache this list for really long time and also update this cached entry in background so that user experience is always smooth.
Some screenshots.
Expected behavior
VM sizes dropdown should be ready in less than 5 seconds
How to reproduce
Try to create a user-cluster with Azure as the provider.
On the screen to add Machine deployment - observe the time taken to populate VM sizes.
Environment
Current workaround
No workaround. I wait for 3 minutes to populate the list.
Affected user persona
Business goal to be improved
Metric to be improved
Potentialy Related ticket
kubermatic/machine-controller#1857 might be also using same API in the background and times out continuously
The text was updated successfully, but these errors were encountered: