Kubernetes explicitly targets the layer below a PaaS (there used to be a nice sliding demo at Google Cloud Next 2017 in SF, with a moving slider between cloud f

Kubernetes explicitly targets the layer below a PaaS (there used to be a nice sliding demo at Google Cloud Next 2017 in SF, with a moving slider between cloud functions and I think either full VM or bare metal). Also, it's drastically simpler than the software it heavily pushed out, and provides a lot of composability and simplification in fact compared to what was there before - but due to needs of flexibility and not being a magical genie (or Sufficiently Advanced Orchestrator) it leaves certain things on the table. What you describe is closer to goals of TOSCA and similar, which are supposed to be parsed by service providers implemented for example on top of Kubernetes or OpenStack or <insert your imagined platform here>. It turns out it's non-trivial, though kubernetes pushing simple standard API interaction led to interesting development in that area.