Should kubelet depend on kubectl and kubernetes-cni? about release

[dgoodwin]

I'm quite new to all this but my current understanding was that on a typical node you will install kubelet, but have no need for kubectl on those hosts, so they should not depend on each other at all.

I'm not really familiar with CNI or the networking, but I thought it was an optional component and kept it off the kubelet deps for time being.

[luxas]

Why not?

I see kubectl as a not-so-heavy-dep, and the most of users want it on their machines.
If they're installing kubeadm which is a CLI tool, kubectl CLI tool is handy to have as well.

[pires]

kubelet doesn't have such dependencies, so I'm in favor of removal.

[mikedanese]

I think we should depend on kubernetes-cni, but I don't think we should depend on kubectl. kubernetes-cni is basically required for core networking functionality like running flannel. e.g. we depend on socat even though port forwarding is an "optional" feature. kubectl on the other hand should only be installed on the master.

We need to do a pass and figure out how we can keep the rpms and debs from drifting.

[luxas]

for me:
kubelet should depend on kubernetes-cni, but not kubectl
kubeadm should depend on both kubectl and kubelet

[yoojinl]

@luxas Why kubeadm should depend on kubectl?

[errordeveloper]

@RustyRobot the instructions in kubeadm docs will refer to kubectl (e.g.
for installing network add-on), so it would be sort of sub-optimal to not
pull it in.

@luxas I recall you have captured all kubelet deps, has that been reflected
in out package specs?

On Tue, 20 Sep 2016, 16:16 Evgeny L, [email protected] wrote:

@luxas https://github.com/luxas Why kubeadm should depend on kubectl?

—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
#97 (comment),
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAPWS91-lU9RTsWGQc79yUTih59FilRfks5qr_i9gaJpZM4KBfxN
.

[luxas]

Documented here: kubernetes/kubernetes#26093 (comment)

I think I covered the most of them already: https://github.com/kubernetes/release/blob/master/debian/xenial/kubelet/debian/control#L13

[yoojinl]

@luxas

Why not?

Well, because it's hard-dependency, which is not required for kubeadm to work.

I see kubectl as a not-so-heavy-dep, and the most of users want it on their machines.
If they're installing kubeadm which is a CLI tool, kubectl CLI tool is handy to have as well.

kubeadm is used to bootstrap the cluster, and there are a couple of servers from which cluster management is performed not from all the minions.

@errordeveloper

the instructions in kubeadm docs will refer to kubectl (e.g. for installing network add-on), so it would be sort of sub-optimal to not pull it in.

We can write in the instruction on the nodes which are required sudo apt-get install kubeadm kubectl

[yoojinl]

If you think that it is what we should do (add kubectl dependency for kubeadm) here is a patch for that #109.