the problem I have with k8s or whole concept of "cloud native" is it almost ONLY focus on web based application, if your application is not HTTP based or "stateless", it is very hard to run or design to be "cloud native" , specially in a managed k8s service(like eks/aks).
Can you tell me what specific challenges you've had with deploying non-HTTP services using Kubernetes? Many features are http-centric, but others seem fairly agnostic to me. What kind of non-http services are we talking about anyway?
one big pain point is that k8s handle inbound (initiated by entity outside of cluster) and outbound connection (initiated by pod) differently and separately, it is difficult to using same public IP address for inbound dst and outbound source, such symmetric is needed for certain applications. I know there is work around for this case, e.g. only uses a single public IP for both inbound and outbound for whole cluster on aks, or use dedicate node, but these workarounds are just workarounds, all have issues.