The second hit is a google+ post wailing “arrrrgh, somebody reinvented borgcfg for Kubernetes” :)
I’m guessing the switch to YAML, even though it might be a bit tedious, was an explicit reaction to the fact that the ultra-programmable borgcfg turned out to cause some big headaches.
The second hit is a google+ post wailing “arrrrgh, somebody reinvented borgcfg for Kubernetes” :)
I’m guessing the switch to YAML, even though it might be a bit tedious, was an explicit reaction to the fact that the ultra-programmable borgcfg turned out to cause some big headaches.