Re: In the OpenShift Origin/CRI-O/Kubernetes effort we have a dilemma.

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 





On 06/30/2018 05:05 PM, Nicolas Mailhot wrote:
Le samedi 30 juin 2018 à 14:22 +0200, Tomasz Torcz a écrit :
BTW, kubernetes package is quite pathological. Installing it brings
kubernetes-master, which contains following four binaries:

-rwxr-xr-x.   3 root root 152M 04-26 11:34 /usr/bin/hyperkube
-rwxr-xr--.   1 root kube 128M 04-26 11:34 /usr/bin/kube-apiserver
-rwxr-xr-x.   3 root root 152M 04-26 11:34 /usr/bin/kube-controller-
manager
-rwxr-xr-x.   3 root root 152M 04-26 11:34 /usr/bin/kube-scheduler

   That's almost 600 MiB (!!!) in 4 binary files. We can forget about
trying to create minimal fedora install image  for cloud, if
installing
single component of k8s triples the installation size.
Yes, Go as a whole is hitting the limits of the "pile lots of third
party code, hide it in vendored tree, think about modularising and APIs
later"

+1

But, the code itself is nice and without major problems, it just needs a
  major injection of release engineering to split what needs splitting
and stabilise what needs stabilising.

+1

The core problem is that people got used to accumulating technical debt
and hoping someone else will take care of it later, and no self-
respecting Go dev wants to tackle this if he can avoid it.


Absolutely -1. Even the super cool Go packaging guidelines will not help. It's the same old story sad story. We need human power + tooling. At best, the tooling will do the hard part and we humans will just decide what to do. It's not about people do not care, it's about people seeing the neverending pile of **** (fill in any word you like, e.g. work) that needs to be done and repeated everytime something is updated. Please, allocated me someone who can spend at least 4hours a day on the tooling I am implementing (and want to implement) and the burden on each package maintainer will get reduced.
_______________________________________________
devel mailing list -- devel@xxxxxxxxxxxxxxxxxxxxxxx
To unsubscribe send an email to devel-leave@xxxxxxxxxxxxxxxxxxxxxxx
Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html
List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines
List Archives: https://lists.fedoraproject.org/archives/list/devel@xxxxxxxxxxxxxxxxxxxxxxx/message/2NQI6SO7QMBMIUGGSVP4VA62XNQJF44N/




[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
[Index of Archives]     [Fedora Announce]     [Fedora Users]     [Fedora Kernel]     [Fedora Testing]     [Fedora Formulas]     [Fedora PHP Devel]     [Kernel Development]     [Fedora Legacy]     [Fedora Maintainers]     [Fedora Desktop]     [PAM]     [Red Hat Development]     [Gimp]     [Yosemite News]

  Powered by Linux