I&#x27;m very heavily working with k8s and while what you say is definitely true, I&#x27;m not too bothered by what I have to configure (aka stuff I can control directly). What I really dislike is stuff on which I have no direct control and that&#x27;s the main problem with k8s. Lot of stuff &quot;just works&quot;, with little-to-no documentation on what are the pieces concurring to make it work nor how it is configured.<p>The &#x27;it just works&#x27; approach might be great with simple scenarios, but it&#x27;s horrible for complex use cases where you need to have detailed control over the pieces that will run in production and - once they are properly setup -, you would anyway automate accordingly your specific usecase.<p>Hence my: &quot;Additional hidden complexity doesn&#x27;t seem to be a good thing in this case&quot;.<p>Beside that, I really have no idea about what they specifically mean with &quot;Kubernetes-based PaaS&quot;. What is it? Abstracting kubernetes cluster setup? If this is the case, i remark that I need more fine-grained access on the internals rather than additional abstractions that internally do &quot;god-knows-what&quot;.