This is the benefit of using managed providers, which don't expect you to have any experience with the Kubernetes control plane. If you don't modify the underlying infrastructure that Porter creates, the chances of a malfunction are quite low (we haven't actually come across a cluster-level issue that wasn't easily resolvable, although I'm sure it'll happen at some point).

Also, if a Kubernetes deployment malfunctions (or any other Kubernetes resource is added incorrectly) and you created it through Porter, it's a bug on our end, and would be dealt with by pushing a fix and requesting that you upgrade that application to the latest version. Along with this, if a Kubernetes deployment fails due to expected behavior (e.g. your worker machines are out of resources), it is our responsibility to propagate that error to the user and give you an easy way to fix it.

Again, there are likely some edge cases for more complicated use-cases, but this has been our experience so far.