kubermatic
Loading Azure VM list takes really long time
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
- UI Version: KKP 2.25.6
- API Version: KKP 2.25.6
- Domain:
- Others:
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
https://github.com/kubermatic/machine-controller/issues/1857 might be also using same API in the background and times out continuously
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Closing https://github.com/kubermatic/dashboard/issues/6492 in favor of this ticket since both require some sort of caching to reduce the lookup time.
Issues go stale after 90d of inactivity.
After a furter 30 days, they will turn rotten.
Mark the issue as fresh with /remove-lifecycle stale.
If this issue is safe to close now please do so with /close.
/lifecycle stale
Stale issues rot after 30d of inactivity.
Mark the issue as fresh with /remove-lifecycle rotten.
Rotten issues close after an additional 30d of inactivity.
If this issue is safe to close now please do so with /close.
/lifecycle rotten
Rotten issues close after 30d of inactivity.
Reopen the issue with /reopen.
Mark the issue as fresh with /remove-lifecycle rotten.
/close
@kubermatic-bot: Closing this issue.
In response to this:
Rotten issues close after 30d of inactivity. Reopen the issue with
/reopen. Mark the issue as fresh with/remove-lifecycle rotten./close
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.