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
kubelet: Refactor RunInContainer/ExecInContainer/PortForward. #6491
kubelet: Refactor RunInContainer/ExecInContainer/PortForward. #6491
Conversation
Thanks for the PR! We've made quite some progress in this direction! :) I may be wrong, but IMO, kubelet should use UID internally, but should also support querying using pod (namespace, name) tuple in public-facing interface. As far as I know, the interface is defined here https://github.com/GoogleCloudPlatform/kubernetes/blob/master/pkg/kubelet/server.go#L99 |
Didn't review PR in detail yet, @yujuhong is right. UID is terrible on user friendly. |
11ce5d2
to
2e11690
Compare
@yujuhong Thank you for clarification! I was wondering why e2e is failing... Maybe this is related. |
2e11690
to
8fe408a
Compare
Replace GetKubeletDockerContainers() with findContainer().
8fe408a
to
ba1ad9f
Compare
LGTM, will wait on your results with e2e. One day, my dream is that we will only use UID internally (and translate full name to UID once we take it in). But it's not currently a priority. |
Just cannot finish e2e because I have a terrible network at home... Will run tomorrow morning when I arrive the company. |
@vmarmol
|
Pretty sure this test failure is not related since it is pointing out an unrelated issue in our system. |
LGTM @yifan-gu! Merging. |
…tainers kubelet: Refactor RunInContainer/ExecInContainer/PortForward.
Replace GetKubeletDockerContainers() with GetPods().
This removes the docker specific code in further. (Now we only have one GetKubeletDockerContainers!)
I remember @dchen1107 said now each pod has its UID, so I think we can remove the podFullName part in the kubelet's interface.(correct me if I am wrong, thank you!).
@vmarmol @yujuhong