The successor will probably be a more integrated platform where it provides a lot of stuff you've got to use sidecars, etc for. Probably a language with good I

The successor will probably be a more integrated platform where it provides a lot of stuff you've got to use sidecars, etc for. Probably a language with good IPC (designed for real distributed systems that handle failover), some unified auth library, and built-in metrics and logging. A lot of real-life k8s complexity is trying to accommodate many supplemental systems for that stuff. Otherwise it's a job scheduler and haproxy.