@sun @shibao @mia Still, I'm watching a k8s demo right now and it's absolutely horrifying, a sea of YAML that a guy is deftly navigating to change one variable and "editing this causes a restart" and magic happens, now your whole cloud is upgraded from OSP 16.2 to OSP 18.01. Meanwhile someone did something like that by accident, IP renumbering happened, and then DHT cannot find any data, users are unhappy. They call our 1st layer support, they call 2nd and the guys mostly put out all the fires, get all the workloads restarted, but data is still not there. Eventually someone pinged me, we found that someone did everything but forgot to actually write out the rings, so everything looked good in builder, but services uses old IPs that they consumed from old compressed rings. The k8s only makes it even more opaque and impossible to fix, even find what's wrong. I hear people say I'd rather support JS in IE6, or program Android, or all sorts of grass is greener stuff.