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

Kubernetes backend should use informer cache for retrieving resources #251

Open
jannfis opened this issue Dec 10, 2024 · 0 comments
Open
Labels
kind/task Tasks, chores, etc optimization Optimization of existing feature
Milestone

Comments

@jannfis
Copy link
Collaborator

jannfis commented Dec 10, 2024

Is your task related to a problem? Please describe.

Right now, the Kubernetes backend for Applications and AppProjects talk directly to the Kubernetes API server when retrieving (e.g. list or get) resources. However, since we use shared informers for both type of resources, we should make use of its caches instead. This will reduce the number of requests being made to the Kubernetes API significantly.

Describe the solution you'd like

The Get and List methods of the Kubernetes backends for Application and AppProject type resources should use the informer's cache instead of reaching out to the API.

Describe alternatives you've considered

Additional context

@jannfis jannfis added kind/task Tasks, chores, etc optimization Optimization of existing feature labels Dec 10, 2024
@jannfis jannfis added this to the v0.2.0 milestone Dec 17, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/task Tasks, chores, etc optimization Optimization of existing feature
Projects
None yet
Development

No branches or pull requests

1 participant