You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
@csviri the issue seems to be that off of a list operation the api server populates the list kind, but not the individual item kinds, so this would affect any generic list operation not just what the informer is using.
When you receive an event, that's just a single resource and does have the kind populated.
We can probably workaround this by setting the kind ourselves.
shawkins
added a commit
to shawkins/kubernetes-client
that referenced
this issue
Jan 29, 2024
Describe the bug
When I create an informer that uses
GenericKubernetesResource
the kind of the existing resources isnull
, sample:It is already
null
in cache.It is strange that, if I create a new
ConfigMap
with the client, it gets propagated properly.Fabric8 Kubernetes Client version
6.10.0
Steps to reproduce
See sample above. Try it with minikube for example.
Expected behavior
Kind field is propagated
Runtime
Kubernetes (vanilla)
Kubernetes API Server version
1.25.3@latest
Environment
Linux
Fabric8 Kubernetes Client Logs
Additional context
No response
The text was updated successfully, but these errors were encountered: