8000 Remove Endpoints caching · Issue #8396 · kiali/kiali · GitHub
[go: up one dir, main page]
More Web Proxy on the site http://driver.im/
Skip to content

Remove Endpoints caching #8396

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.

Sign up for GitHub

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

Jump to bottom
Open
nrfox opened this issue May 2, 2025 · 4 comments
Open

Remove Endpoints caching #8396

nrfox opened this issue May 2, 2025 · 4 comments
Assignees
@hhovsepy
Labels
enhancement This is the preferred way to describe new end-to-end features.

Comments

@nrfox
Copy link
Contributor
nrfox commented May 2, 2025

What do you want to improve?

Kiali caches Endpoints which change very often in large clusters and can consume a lot of resources. Kiali only uses the endpoints for matching services to pod ips. The pod ips can be gotten from the pod status itself rather than from Endpoints so there's no need to use Endpoints.

Before/after resource consumption comparison will need to be included with this.

What is the current behavior?

Kiali caches Endpoints.

What is the new behavior?

Kiali uses pod status to get pod ips rather than Endpoints.

Probably blocked by #8355
@nrfox nrfox added the enhancement This is the preferred way to describe new end-to-end features. label May 2, 2025
@nrfox
Copy link
Contributor Author
nrfox commented May 13, 2025

Another reason is that Endpoints is now deprecated: https://kubernetes.io/blog/2025/04/24/endpoints-deprecation/

@jshaughn
Copy link
Collaborator

@nrfox Promoting to sprint given that #8355 is merged. Sound good?

@nrfox
Copy link
Contributor Author
nrfox commented May 13, 2025

Sure there's nothing blocking this now and the change should be fairly small. What needs to be included with this is a resource usage comparison of before and after this change. How much memory Kiali uses in a reasonably sized cluster before this change vs. after to show an improvement.

@hhovsepy hhovsepy mentioned this issue May 21, 2025
Open
@hhovsepy
Copy link
Contributor
hhovsepy commented May 21, 2025 •
edited
Loading

How we can make this kind of precise measurement of memory usage when only the Endpoints were removed from the cache? Will the improvement size be bigger than the environment's unstability? Because cypress perf tests for ServiceDetails page did not show any improvement.

@hhovsepy hhovsepy moved this from 📋 Backlog to 🏗 In progress in Kiali Sprint 25-08 | Kiali v2.11 May 22, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
517C
Assignees

@hhovsepy hhovsepy

Labels
enhancement This is the preferred way to describe new end-to-end features.
Projects
Kiali Sprint 25-08 | Kiali v2.11
Status: 🏗 In progress
Milestone
No milestone
Development

No branches or pull requests
3 participants
@hhovsepy @jshaughn @nrfox
0