APIListChunking - feature gate to GA?

[tengqm]

What would you like to be added:

Shall we graduate APIListChunking to GA? The feature has been on since v1.9 and we are not getting a lot of complaints/issues on this feature (I may be wrong).

Why is this needed:

	// owner: @smarterclayton
	// alpha: v1.8
	// beta: v1.9
	//
	// Allow API clients to retrieve resource lists in chunks rather than
	// all at once.
	APIListChunking featuregate.Feature = "APIListChunking"

[tengqm]

/sig api-machinery

[fedebongio]

/assign @smarterclayton
/triage accepted

[carlory]

/assign

[pacoxu]

The KEP-Issue

kubernetes/enhancements#365, Taken from #49338. Original discussion in #2349

• The KEP is https://github.com/kubernetes/enhancements/tree/master/keps/sig-api-machinery/365-paginated-lists moved to enhancements from the community by @deads2k.
• The original design is kubernetes/community which is created by Design for consistent API chunking in Kubernetes community#896.

Implementation PRs are

alpha 1.8 initialized by @smarterclayton

• Disable default paging in list watches Disable default paging in list watches #51876
• Alpha list paging implementation Alpha list paging implementation #48921

beta 1.9 promoted by @smarterclayton

• Enable API chunking and promote to beta for 1.9 Enable API chunking and promote to beta for 1.9 #52949
• Support api chunking in kubectl get Support api chunking in kubectl get #53768
• Table printers and server generation should always copy ListMeta Table printers and server generation should always copy ListMeta #55835

1.15 enhanced by @jpbetz

• Paginate watch cache->etcd List calls & reflector init/resync List calls not served by watch cache Paginate watch cache->etcd List calls & reflector init/resync List calls not served by watch cache #75389
• Add ListPager.EachListItem util Add ListPager.EachListItem util #75849

1.18 fix issues by @wojtek-t

• Don't paginate in listwatch Don't paginate in listwatch #86790
• Avoid thundering herd of relists on etcd Avoid thundering herd of relists on etcd #86430

1.20 new consumers

• Switch GCP list calls to paginated calls. Switch GCP list calls to paginated calls. #96278

/cc @wojtek-t @jpbetz @smarterclayton

[pacoxu]

As the current process, it needs a PPR process in https://github.com/kubernetes/enhancements to decide whether this feature should be GA in the next release cycle.

You should get feedbacks and answer the questions in KEP PRR to make sure whether the feature should be promoted.

[JohnRusk]

I've logged a concern about the current behaviour in the linked issue #102672

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

[k8s-ci-robot]

@k8s-triage-robot: Closing this issue.

In response to this:

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Reopen this issue or PR with /reopen
• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[ehashman]

/remove-lifecycle rotten
/reopen

[k8s-ci-robot]

@ehashman: Reopened this issue.

In response to this:

/remove-lifecycle rotten
/reopen

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[wojtek-t]

I'm going to take it - will send out KEP update after code freeze to address the pagination in watchcache which seems to be the biggest blocker now.

[wojtek-t]

/remove-lifecycle stale
/assign

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough active contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle rotten

[wojtek-t]

/remove-lifecycle rotten

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[wojtek-t]

/remove-lifecycle stale

[k8s-triage-robot]

The Kubernetes project currently lacks enough contributors to adequately respond to all issues and PRs.

This bot triages issues and PRs according to the following rules:

• After 90d of inactivity, lifecycle/stale is applied
• After 30d of inactivity since lifecycle/stale was applied, lifecycle/rotten is applied
• After 30d of inactivity since lifecycle/rotten was applied, the issue is closed

You can:

• Mark this issue or PR as fresh with /remove-lifecycle stale
• Mark this issue or PR as rotten with /lifecycle rotten
• Close this issue or PR with /close
• Offer to help out with Issue Triage

Please send feedback to sig-contributor-experience at kubernetes/community.

/lifecycle stale

[wojtek-t]

/remove-lifecycle stale

[tallclair]

/priority important-longterm

[wojtek-t]

This was graduated to GA in 1.29 with: #119503

[davidopp]

Is this feature used in the golang or Java client library? If not, is there a plan to use it?

[jpbetz]

Is this feature used in the golang or Java client library? If not, is there a plan to use it?

It has been in use for a long time in client-go. I don't know about the Java client offhand.

[wojtek-t]

It has been in use for a long time in client-go.

You need to set the limit though if you want to use it.