Snapshottable API server cache

[serathius]

Enhancement Description

• One-line enhancement description (can be used as a release note): Improve apiserver watch cache to serve pagination.

• Kubernetes Enhancement Proposal: https://github.com/kubernetes/enhancements/blob/master/keps/sig-api-machinery/4988-snapshottable-api-server-cache/README.md

• Discussion Link: SIG api machinery August 21 meeting https://docs.google.com/document/d/1x9RNaaysyO0gXHIr1y50QFbiL1x8OWnk2v3XnrdkT5Y/edit?tab=t.0#heading=h.jnlasazf8f1g

• Primary contact (assignee): serathius@

• Responsible SIGs: api-machinery

• Enhancement target (which target equals to which milestone):

  • Alpha release target (x.y): 1.33
  • Beta release target (x.y):
  • Stable release target (x.y):

• Alpha

  • KEP (k/enhancements) update PR(s): Snapshottable API server cache #5017
  • Code (k/k) update PR(s):
    • Test continuations and exact revision LISTs kubernetes#130242
    • Watchcache snapshot kubernetes#130279
    • Refactor TestList to allow testing continuations and exact kubernetes#130280
    • Remove limit support from btree store kubernetes#130443
    • Pass storage.ListOptions to WaitUntilFreshAndList kubernetes#130589
    • Test recursive in TestGetListCacheBypass and separate overrides kubernetes#130588
    • Serve LISTs with exact RV and continuations from cache kubernetes#130423
    • Implement consistency checking kubernetes#130475
  • Docs (k/website) update PR(s):
    • KEP-4988 documentation changes website#49941

• Beta

  • KEP (k/enhancements) update PR(s):
    • Consider introducing time based compaction for watch cache
  • Code (k/k) update PR(s):
    • Re-enable conformance test Disable ListFromCacheSnapshot in ci-kubernetes-network-kind-alpha-beta-features test-infra#34587
  • Docs (k/website) update(s):

[serathius]

/sig api-machinery

[fuweid]

Hi @serathius the discussion link is private?

[serathius]

No, it's api-machinery document, so requires you to be part of the apimachinery mailing list.

[jpbetz]

@serathius Is the intent to target alpha for 1.33 or is this future work? There's already a ton of work going on in the watch cache, so I'm perfectly happy to focus on the ongoing efforts for 1.33, but wanted to check to make sure I set milestones and lead-opt-in correctly.

[serathius]

My goal is to target v1.33, It might be hard to get review from @deads2k

[serathius]

/milestone v1.33

[pacoxu]

@jpbetz @dipesh-rawat this is target to v1.33 and the KEP was merged.
Should the lead-opted-in and tracked label be added and tracked by release team?