What we learned after a year on Kubernetes

Re:What we learned after a year on Kubernetes by justicezyx on Wednesday September 16, 2020 @07:36PM (#24499361)

Insider joke:

K8s was born to solve the same problem Borg solved or simply design in such a way to not have that problem.

One of them is the config files hell.

Borgcfg files ranks #3 in terms of line count across all of Google. (Borgcfg language is similar to Jsonnet, helm)

In terms of the amount of power wielded buy a single CLI, `borgcfg`, this little program that has less than 50k lines of nontesting code, stands at a peak dwarfs almost anything else inside Google.

I declared in 2015 that k8s will eventually enjoy the same borgcfg problem. And I was advocating code driving application management approach as you suggested, not the configuration as code (behind the infrastructure as code facade).

Well, it seems I am still on the track to be on the correct camp...

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by esprehn on Wednesday September 16, 2020 @08:18PM (#24499699)

Relevant thread (with you) from the nearby past: https://news.ycombinator.com/item?id=20849454

The yaml monster in k8s is quite unpleasant. It's always been surprising to me how we somehow ended up with executable BUILD files but totally static deploy files.

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by sandGorgon on Thursday September 17, 2020 @01:09AM (#24501385)

What do you think about Cue ? There's a very interesting issue about why Cue improves upon Borg.

https://github.com/cuelang/cue/issues/33#issuecomment-483615...

[ Parent | on HN ]

Re:What we learned after a year on Kubernetes by justicezyx on Thursday September 17, 2020 @01:58AM (#24501650)

Sorry, I have little knowledge on Cuelang.

@mpvl is one of my most admired Googler. I promised to contribute to the Cue project, but haven't found time (typical startup employee situation, but it seems there is no trouble to find time surfing hacker news...).

[ Parent | on HN ]