3 ms·
The funny thing about the situation you describe is that there are real world examples of similar circular dependencies. I recall GitHub having an issue like t
by koolba 10y ago
The funny thing about the situation you describe is that there are real world examples of similar circular dependencies.
I recall GitHub having an issue like that where their build pipeline used Bower which is hosted on GitHub. When shit hit the fan and a build broke the site, they could build the "fix" as Bower didn't work.
- jzelinskie 10y agoMy own experience working at CoreOS is that many of our projects exploit self-referentiality as it's a particularly useful property. Off the top of my head: - Quay.io, our registry service, is built and deployed by itself - Clair, our static analysis tool for detecting security vulnerabilities, analyzes itself - Tectonic, our enterprise Kubernetes distro, is "self-driving" and manages itself - discovery.etcd.io, a service we run to make it easier to bootstrap new etcd quorums, is just a quorum of etcd nodes
- deleted 10y ago[deleted]
- takeda 9y agoI think you are missing the point. It's like running docker registry on kubernetes. If for some reason the cluster goes down, bootstrapping it might be a bit difficult.
- koolba 9y agoYes that's the exact point I was trying to make. Things are fine until they're not, at which point it's surgery and tribal knowledge to fix them.