Using Kubernetes in Azure (and this might be Azure specific), there isn't enough easy diagnostics via point/click for production issues. It is a nightmare trying to figure out why something happened and feels like you need to gain more expertise (at time sensitive times!) each time it does. Azure has improved over the years in this regard. But it might be a Kubernetes thing.
A cool feature would be "This pod stopped, and didn't restart for 10 minutes" and the reason is "{the reason in plain English}".
Kubernetes feels like a leaky thing to throw abstractions over, so the pain with using it is you need to become an expert in it, more so than the serverless offerings that are more genuinely abstracted, like the various app platforms that run the containers directly, or functions.
I guess even when managed by the cloud host, it is more serverful (e.g. the need to SSH into VMs to do security hardening checks), but then there is this beast running on those servers you need to understand too.
And at that point you need a lot of engineer time anyway and probably a platform separation to deal with it all.
So I think if your product could remove some of those kinds of issues it would be good - but then I am still trying to work out "why choose Kubernetes and not some sort of app service" for the majority of users (I am keeping an open mind!)