buckaroogeek/copr-k8s-refresh

Decision Point - Which binaries to produce?

Opened this issue · 0 comments

The current (4 Sept 2022) kubernetes spec file generates binaries for kubectl, kubeadm, kublet, kube-proxy, kube-apiserver, kube-controller, and kube-scheduler. Upstream makefile includes the following in the ./cmd directory:

[bgsmith@pico kubernetes (rawhide %)]$ ls cmd
clicheck                            genyaml                   kubemark
cloud-controller-manager  importverifier           kube-proxy
dependencycheck             kubeadm                 kube-scheduler
gendocs                            kube-apiserver        linkcheck
genkubedocs                    kube-controller-manager  OWNERS
genman                            kubectl                     preferredimports
genswaggertypedocs       kubectl-convert       genutils                  
kubelet

Upstream rpms provide kubectl, kubeadm, and kubelet. And upstream documentation to create a cluster only refers to these three binaries.

Should the revised spec file only produce kubeadm, kubectl, kubelet?