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

Loading Azure VM list takes really long time #6808

Open
dharapvj opened this issue Sep 5, 2024 · 3 comments
Open

Loading Azure VM list takes really long time #6808

dharapvj opened this issue Sep 5, 2024 · 3 comments
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/ui Denotes a PR or issue as being assigned to SIG UI.
Milestone

Comments

@dharapvj
Copy link

dharapvj commented Sep 5, 2024

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.
image

image

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

kubermatic/machine-controller#1857 might be also using same API in the background and times out continuously

@dharapvj dharapvj added kind/bug Categorizes issue or PR as related to a bug. sig/ui Denotes a PR or issue as being assigned to SIG UI. labels Sep 5, 2024
@ahmedwaleedmalik
Copy link
Member

/milestone KKP 2.27

@kubermatic-bot kubermatic-bot added this to the KKP 2.27 milestone Sep 27, 2024
@kubermatic-bot
Copy link
Contributor

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

@kubermatic-bot kubermatic-bot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Dec 26, 2024
@dharapvj
Copy link
Author

dharapvj commented Jan 2, 2025

/remove-lifecycle stale

@kubermatic-bot kubermatic-bot removed the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label Jan 2, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Categorizes issue or PR as related to a bug. sig/ui Denotes a PR or issue as being assigned to SIG UI.
Projects
None yet
Development

No branches or pull requests

3 participants