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
Kiali has a homegrown kube cache implementation that offers an abstraction over managing informers and listers. Controller-runtime has its own cache abstraction that does all the things that Kiali needs and it makes it easier to integrate into controllers. Kiali already uses controller-runtime to manage the validation controller but does not use controller-runtime client/cache. Without adopting the controller-runtime client/cache, it is more difficult to develop new controllers and for the validation controller to do per object validations. We also do not want to use two different sets of informers (Kiali home grown cache and controller-runtime cache) since we could end up caching the same objects twice.
The text was updated successfully, but these errors were encountered:
What do you want to improve?
Kiali has a homegrown kube cache implementation that offers an abstraction over managing informers and listers. Controller-runtime has its own cache abstraction that does all the things that Kiali needs and it makes it easier to integrate into controllers. Kiali already uses controller-runtime to manage the validation controller but does not use controller-runtime client/cache. Without adopting the controller-runtime client/cache, it is more difficult to develop new controllers and for the validation controller to do per object validations. We also do not want to use two different sets of informers (Kiali home grown cache and controller-runtime cache) since we could end up caching the same objects twice.
The text was updated successfully, but these errors were encountered: