I needed to run a container in the cloud. Not a microservices platform. Not a service mesh. Just one container, one port, accessible from the internet. Here's how OCI Container Instances turned out to be the right tool.

Why I Stopped Reaching for Kubernetes First

I'll be honest — I'm a Kubestronaut. I have all the CNCF Kubernetes certifications. My default muscle memory is kubectl apply -f for everything. But last month I needed to deploy a small Go API for a side project and I caught myself writing a Helm chart for a single container.

That felt ridiculous.

The API had two endpoints. It needed 256MB of RAM. There was no reason to stand up a control plane, configure node pools, set up an ingress controller, and maintain all of that just to serve JSON over HTTP.

I'd used OCI Container Instances before for a quick test and remembered it being dead simple. So I tried it for real this time.

What OCI Container Instances Actually Are

The closest analogy is docker run but Oracle manages the host.…