-
Notifications
You must be signed in to change notification settings - Fork 3.4k
LRP: Add explicit dependency to k8s ServiceCache #32796
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
LRP: Add explicit dependency to k8s ServiceCache #32796
Conversation
/test |
d5cb61b
to
b13fdce
Compare
rebased to |
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
nit: Can you revert the white space changes if they weren't added by a standard golang style check linter?
Currently, the Agent daemon setup registers the k8s `ServiceCache` with the LRP Manager via the method `RegisterSvcCache`. In the meantime, the k8s `ServiceCache` is provided by its own Hive Cell which makes it possible to have an explicit dependency from the LRP Manager to the `ServiceCache`. Therefore, this commit adds the k8s `ServiceCache` as direct dependency to the LRP Manager and removes the method `RegisterSvcCache`. Signed-off-by: Marco Hofstetter <marco.hofstetter@isovalent.com>
b13fdce
to
e105ffb
Compare
/test |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Makes sense to me 👍
Currently, the Agent daemon setup registers the k8s
ServiceCache
with the LRP Manager via the methodRegisterSvcCache
.In the meantime, the k8s
ServiceCache
is provided by its own Hive Cell which makes it possible to have an explicit dependency from the LRP Manager to theServiceCache
.Therefore, this commit adds the k8s
ServiceCache
as direct dependency to the LRP Manager and removes the methodRegisterSvcCache
.