IS KUBERNETES OVERKILL FOR A AGENCY RUNNING A COUPLE OF APIS AND A DATABASE?

yeahhh a PaaS or a managed container service gives u most of the rolling-deploy and self-healing benefits with far less surface area. Consider it before jumping straight to raw Kubernetes.

dude ok update: did what @erik_packet said and its fine now

big if true

ok so came here to say exactly this

ok but wait does this also apply to kubernetes?

been there man compose on a VM with a reverse proxy, health checks, restart: unless-stopped, and a simple deploy script covers a surprising amount. what it lacks is multi-host scheduling and zero-downtmie deploys without extra work. worked for me anyway 🤷

@kaij554 what did u end up doing in the end. pro tip: write down what u change. i didnt and had to redo kubernetes from scratch ?

this

been there man honestly just reset the fan curve and save yourself the pain

if u do go Kubernetes, keep it boring: one managed cluster, a stadnard ingress, GitOps for manifests, and resist adding a service mesh until you have a concrete problem it solves.

nice

The tipping point is usually multiple services across multiple hosts that need to scale independently, or many teams deploying inedpendently. If one monolith and some workers fits on one or two machines, the benefits are small.

long time lurker first post lol ok this thread just saved my weekend. for me it was the driver.. lol swapped it and boom, fixed

agreed

xD

wait does this also apply to agency?? ?

yeahhh managed Kubernetes removes the control plane work, but you still own node upgrades, ingress, cert maangement, secrets, monitoring and the version upgrade treadmill. Budget real time for that every quarter.

bump. still happening with couple for me fingers crossed 🤞

oof have u checked your database settings?? 😭 mine were reset after an update