3 ms·
> Great opportunity for someone ballsy to write a book about kubernetes internals for the general engineering population. What would be the interest of it? Thi
by motorest 2y ago
> Great opportunity for someone ballsy to write a book about kubernetes internals for the general engineering population.
What would be the interest of it? Think about it:
- kubernetes is an interface and not a specific implementation,
- the bulk of the industry standardized on managed services, which means you actually have no idea what are the actual internals driving your services,
- so you read up on the exact function call that handles a specific aspect of pod auto scaling. That was a nice read. How does that make you a better engineer than those who didn't?
- arijo 2y agoI don't really care about the standardized interface. I just want to know how you'd implement something that would load your services and dependencies from a config file, bind them altogether, distribute the load through several local VMs and make it still work if I kill the service or increase the load. In less than 1000 lines.
- motorest 2y ago> I don't really care about the standardized interface. Then you seem to be confused, because you're saying Kubernetes but what you're actually talking about is implementing a toy container orchestrator.