Usually,. the thing that you lose is scalability, availability any reliability.

You will need a remote backup and a secondary located service, just in case. Potentially a third development one to not push breaking changes directly into production.

Skipping any of this will make your service brittle in addition to not being scalable.

And it already hits the rule of three... (of "don't repeat yourself") that makes a lightweight Kubernetes deployment worthwhile. (Perhaps without all the bells and whistles.)

Remember, downtime is usually lost money. A day's worth can be thousands of dollars at least, and that's two nines already. (99.99%)