javascript icon indicating copy to clipboard operation
javascript copied to clipboard
verified publisher icon kubernetes-client

Version 1.0.0+ expected Informer regression?

Open WeetA34 opened this issue 8 months ago • 1 comments

Describe the bug Starting client 1.0.0, I noticed two things which have been reverted to a 5/6 years old versions:

  • the informer interface doesn't "support" anymore ErrorCallback for on/off("connect", ...) and on/off("error", ...)
  • the makeInformer function returns an Informer<T> instead of Informer<T> & ObjectCache<T>

Both things above have been introduced 3 years ago. So, i was wondering if it's expected to have reverted these to an old version?

version 0.22.3

Image

version 1.0.0+

Image

Thank you

Client Version 1.0.0+

Server Version N/A

To Reproduce N/A

Expected behavior Same behavior as 0.22.3

Example Code N/A

Environment (please complete the following information):

  • OS: N/A
  • Node.js: N/A
  • Cloud runtime: N/A

Additional context N/A

WeetA34 avatar May 23 '25 12:05 WeetA34

We definitely forked to produce the 1.0 branch a long time ago and not everything got ported between the branches while we had both active. Feel free to cherry-pick/port and send PRs.

brendandburns avatar May 24 '25 18:05 brendandburns

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

k8s-triage-robot avatar Aug 22 '25 18:08 k8s-triage-robot

The Kubernetes project currently lacks enough active 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 rotten
  • Close this issue with /close
  • Offer to help out with Issue Triage

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

/lifecycle rotten

k8s-triage-robot avatar Sep 21 '25 18:09 k8s-triage-robot