TODO list

[tg123]

• remove websocket, using http2
• generate WatchXXX for easier api
• remove remaining autorest package
• refactor KubernetesClientConfiguration and Kubernetes, too many duplicate fields
• ask chatgpt to impl kubectl

[lqlive]

generate WatchXXX for easier api

Hi @tg123 Regarding this, are we planning to use the latest watch endpoint from Kubernetes OpenAPI?

[tg123]

@lqlive no, will not use deprecated /watch i remember k8s decided to remove this in 1.30.

[lqlive]

@lqlive no, will not use deprecated /watch i remember k8s decided to remove this in 1.30.

/watch has been deprecated, In this case, do we have to manually generate Watchxxx methods? Can I know more details about how to implement this feature? I would like to submit a PR to implement this feature.

[tg123]

planned to generate watch=true and remove watch from list

i am ready to welcome your PR

[k8s-triage-robot]

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

This bot triages un-triaged issues 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 as fresh with /remove-lifecycle stale
• Close this issue with /close
• Offer to help out with Issue Triage

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

/lifecycle stale