Skip to content

k8s client vs fabric8 discovery implementation #2118

@wind57

Description

@wind57

In the k8s client, our discovery implementation is based on listers:

Lister<V1Service> ...
Lister<V1Endpoints> ...

In contrast, in fabric8 we query for the data on demand every time we need it, or in other terms, we do not use listers.

I think fabric8 should align here. I am basing my understanding on the fact that k8s client implementation was done after fabric8, so I assume listers are the way we wanna go for both clients.

Let me know what you think, and I can start working in one of the directions. Thank you

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions