knative / knative/eventing

Flag to disable caching on ApiServerSource adapter

Open
#8,642 7 comments 0 reactions 2 assignees View on GitHub

@Ankitsinghsisodya is already working on this.

Since Apr 21, 2026.

kind/feature-request triage/accepted
Dominant language
Go
Stars
1.6k
Forks
631
Avg merge
3d 13h
Merged PRs (30d)
6

Description

Problem
We do have an ApiServerSource tracking 5 resources across 1000+ namespaces which results into a lot of:

I0718 14:02:19.224595 1 request.go:697] Waited for 17m12.738947279s due to client-side throttling, not priority and fairness, request: GET:https://172.30.0.1:443/apis/tekton.dev/v1/namespaces/.../taskruns?limit=500&resourceVersion=0

due to the number of requests (5 resources * 1000+ namespaces = ~5000).

We would like to have a flag in the ApiServerSource propagated to the Adapter Deployment so it does not cache.

Persona:

System Operator: wants to reduce load in Kubernetes.

Exit Criteria

There are no caching calls from the adapter container.

Time Estimate (optional):

I would say that pure code would be ~24 hours of good quality coding time.

Additional context (optional)
I need to develop a reproducer.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.