Closed Jeffwan closed 4 years ago
@gaocegege Address the feedbacks, please have another look
LGTM but could you add some notes in the forked code so we can always look back what we did and where the code was forked from (with version/link).
+1 for this suggestion.
/lgtm
@gaocegege @terrytangyuan
Thanks for the review. That's great suggestion. I will file a follow up PR to add a CONTRIBUTING.md doc and include these technical details.
OK, then I think we can merge this one.
/approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: terrytangyuan
The full list of commands accepted by this bot can be found here.
The pull request process is described here
This PR aims to solve following issue and it also help to remove more direct dependency on Kubernetes. Resolve part of #48 #71
Background
Current implementation uses
PodControlInterface
andPodControllerRefManager
fromk8s.io/kubernetes/pkg/controller
and self-implementedServiceControlInterface
andServiceControllerRefManager
which bring some problems.service_ref_manager
which is kind of unclear until I find #36Solution
Consider the situation that Kubernetes upstream doesn't have implementation of
ServiceControlInterface
andServiceControllerRefManager
, I would suggest we just folkPodControlInterface
andPodControllerRefManager
locally.This help remove dependency a lot and we can also make sure pods/service implementation can be updated at the same time.
In addition, I will make some efforts to this issue. https://github.com/kubernetes/client-go/issues/332. I will try to submit a PR and see feedbacks. If change can be accepted, then we don't need to maintain these auxiliary codes on our side.
/cc @gaocegege @terrytangyuan
Need @gaocegege 's review on code folk since he originally worked on this.