5 ms·

... requiredDuringSchedulingIgnoredDuringExecution: ... This instantly remembered me of this: https://thedailywtf.com/articles/the-longest-method h

by haolez 6y ago

... requiredDuringSchedulingIgnoredDuringExecution: ... This instantly remembered me of this: https://thedailywtf.com/articles/the-longest-method https://thedailywtf.com/articles/the-longest-method Kubernetes sometimes shows its Java roots.

vsareto 6y ago
That Java link in the article goes to a completely not-Java Chinese site btw
- Igelau 6y ago
  And the Spring link is a 404
tomnipotent 6y ago
To be fair, I don't see how this could be shorter in any other language without losing readability.
- yongjik 6y ago
  You don't have to. Kubernetes should just say "required" here, and the documentation should say "Warning: this is only checked during scheduling." printf isn't named printIntoBufferWhichMayNotFlushUntilLinefeed, and people are fine with it.
  - dharmab 6y ago
    I believe there may have been a plan to allow checks during runtime at some point; although this feature is no longer necessary since https://github.com/kubernetes-sigs/descheduler#removeduplicates https://github.com/kubernetes-sigs/descheduler#removeduplica... can do it.
- kerny 6y ago
  They could have used: soft, hard and strict with the documentation explaining the differences.
ithkuil 6y ago
> its Java roots Citation needed. AFAIR Borg is implemented in C++ and k8s has been implemented in Go from day 0. Am I missing some crucial steps in k8s's history?
- enitihas 6y ago
  I remember a comment from someone on the go team (bradfitz maybe) saying that the initial plan for Kubernetes was to be implemented in java, but go was chosen because it already had a lot of momentum in the container world.
- detaro 6y ago
  Apparently the first version was based on a Java prototype, but it's unclear to me how much that's visible: https://kubernetes.io/blog/2018/06/06/4-years-of-k8s/ https://kubernetes.io/blog/2018/06/06/4-years-of-k8s/ > Concretely, Kubernetes started as some prototypes from Brendan Burns combined with ongoing work from me and Craig McLuckie to better align the internal Google experience with the Google Cloud experience. Brendan, Craig, and I really wanted people to use this, so we made the case to build out this prototype as an open source project that would bring the best ideas from Borg out into the open. > After we got the nod, it was time to actually build the system. We took Brendan’s prototype (in Java), rewrote it in Go, and built just enough to get the core ideas across

by haolez 6y ago

vsareto 6y ago

That Java link in the article goes to a completely not-Java Chinese site btw

Igelau 6y ago
And the Spring link is a 404

tomnipotent 6y ago

To be fair, I don't see how this could be shorter in any other language without losing readability.

yongjik 6y ago
You don't have to. Kubernetes should just say "required" here, and the documentation should say "Warning: this is only checked during scheduling." printf isn't named printIntoBufferWhichMayNotFlushUntilLinefeed, and people are fine with it.
- dharmab 6y ago
  I believe there may have been a plan to allow checks during runtime at some point; although this feature is no longer necessary since https://github.com/kubernetes-sigs/descheduler#removeduplicates https://github.com/kubernetes-sigs/descheduler#removeduplica... can do it.
kerny 6y ago
They could have used: soft, hard and strict with the documentation explaining the differences.

ithkuil 6y ago

> its Java roots Citation needed. AFAIR Borg is implemented in C++ and k8s has been implemented in Go from day 0. Am I missing some crucial steps in k8s's history?

enitihas 6y ago
I remember a comment from someone on the go team (bradfitz maybe) saying that the initial plan for Kubernetes was to be implemented in java, but go was chosen because it already had a lot of momentum in the container world.
detaro 6y ago
Apparently the first version was based on a Java prototype, but it's unclear to me how much that's visible: https://kubernetes.io/blog/2018/06/06/4-years-of-k8s/ https://kubernetes.io/blog/2018/06/06/4-years-of-k8s/ > Concretely, Kubernetes started as some prototypes from Brendan Burns combined with ongoing work from me and Craig McLuckie to better align the internal Google experience with the Google Cloud experience. Brendan, Craig, and I really wanted people to use this, so we made the case to build out this prototype as an open source project that would bring the best ideas from Borg out into the open. > After we got the nod, it was time to actually build the system. We took Brendan’s prototype (in Java), rewrote it in Go, and built just enough to get the core ideas across