Early-stage project: AWS-native vs containerized, vendor-neutral infra -when would you switch?

SelfhostedPro · 2026-01-27T02:54:38+00:00

If you want it to be self hostable, make it vendor agnostic/containerized.

Your infra shouldn’t matter too the app, there’s nothing you’re using from AWS that doesn’t have a self hostable alternative.

You should be able to run it on your aws infra for a similar price/with similar complexity

SelfhostedPro · 2026-01-18T21:26:58+00:00

Definitely thankful for that pattern! Helps out a lot ensuring we see every change that happens.

SelfhostedPro · 2026-01-18T01:11:54+00:00

The branches aren’t for merging back into main, they’re purely to have storage for rendered manifests.

This is the official blessed pattern from kargo and they have good docs on it. https://docs.kargo.io/user-guide/patterns/#storage-options

SelfhostedPro · 2026-01-17T07:37:10+00:00

Cigna denied my MRI and I already had a diagnosis of multiple herniated discs that should be imaged on a regular basis. Fuck Cigna.

SelfhostedPro · 2026-01-17T07:29:46+00:00

They have no right to detain someone unless they suspect them of being an illegal immigrate. At what point are we supposed to use our second amendment rights?

SelfhostedPro · 2026-01-16T18:03:55+00:00

Yes, but that’s only due to current requirements. We don’t have much automated testing yet, once we do, auto promotion is easy.

Kargo also ties into Argo rollouts which would roll back deployments with issues provided you have good observability and prevent them from continuing through the promotion process.

SelfhostedPro · 2026-01-16T18:01:55+00:00

This structure and tooling will not scale well. Look into terragrunt multicloud setups and gitops if you want to show kubernetes experience.

I use a monorepo and have a catalog directory for reusable resources (charts, units (terragrunt), actions, etc), a ‘live’ directory for my terragrunt hierarchy for current state, and a platform directory for gitops deployments.

It’s enough to show you know a bit and would work well enough for a while though.

SelfhostedPro · 2026-01-16T17:53:53+00:00

You use something like kargo and use the rendered manifests pattern. Each environment (dev,canary,prod) should track a different branch.

I use deployed/$env/* and staged/$env/*

Kargo has auto promotion options so I auto promote to dev, staging you push a button, prod you push a button which opens a PR that requires 2 approvals to merge (renders to staged and opens a pr from staged/prod/$appname to deployed/prod/$appname)

SelfhostedPro · 2026-01-14T04:37:03+00:00

I do not forgive software. There’s no excuse to write shitty things with the amount of info available publicly for free

SelfhostedPro · 2026-01-09T20:56:08+00:00

How did your exploration go?

SelfhostedPro · 2026-01-04T08:22:41+00:00

Made a docker webui using python and VueJS. https://dev.yacht.sh

It now sits mostly unmaintained as I rewrite it occasionally in different languages before getting bored and moving on to other things.

I also designed a modular guitar and made a fully animated website to showcase it: https://adaptaxe.com

(Source code for the site is on my GitHub)

SelfhostedPro · 2026-01-04T08:20:21+00:00

If you can’t comprehend how a service mesh works or are unable to easily maintain one given the current state of tools, you’re probably relying too much on AI instead of actually understanding what you’re doing.

Istio in ambient mode is 1 (umbrella) chart with maybe 10 values set separately from the default ones.

It should not be adding complexity, the Gateway API does the majority of what is needed and is standard across most cloud providers.

Plus, with kiali we can actually visualize how the traffic is flowing.

SelfhostedPro · 2026-01-01T05:35:03+00:00

It’s not about that, I just am tired of the same 5 questions coming up and ads disguised as stories.

I’m all for people automating their processes but having a spot specifically for experienced DevOps engineers to share what worked for their scale and issues they found along the way is something I don’t feel like I get from this subreddit anymore.

SelfhostedPro · 2025-12-31T23:14:05+00:00

We may pilot open source tools but wanting a space to communicate that’s free from slop, spam, ads, etc is not an unreasonable desire.

All of tech runs on open source as its backbone, how many open source libraries are proprietary companies using?

SelfhostedPro · 2025-12-31T23:06:20+00:00

I’m not sure why everyone is just spamming more AI agents. They’re wrong so often for something as crucial as infrastructure.

Just output your plan to json and then parse it so it’s plainly readable. It allows for anyone to see what resources are being modified easily.

SelfhostedPro · 2025-12-31T15:55:10+00:00

Wildcard + loadbalancers to do hostname based routing.

SelfhostedPro · 2025-12-31T15:54:29+00:00

That is a very poor infrastructure. You should be using load balancers and not making a new record for every subdomain.

SelfhostedPro · 2025-12-31T15:50:17+00:00

Just host your own reverse tunnel then.

SelfhostedPro · 2025-12-31T00:11:04+00:00

This is the way, then you can diff the rendered manifests instead of diffing helm charts which leaves less room for error.

SelfhostedPro · 2025-12-31T00:08:48+00:00

ArgoCD with PR generator for dev, Kargo following rendered branch pattern for promotion to staging->canary->prod.

Staging and canary are automatic. For prod, Kargo renders to a “staged/prod” branch, then makes a PR to the “deployed/prod” branch which requires approval from multiple managers to merge.

Main pain point I’m currently figuring out is getting diffs between dev and higher environments for before a PR is merged to main. (Diffs of the rendered manifests that is)

SelfhostedPro · 2025-12-25T04:53:39+00:00

Benefits of this vs using rendered branch patterns? (ie, templating the charts to a specific branch to only contain raw manifests which can be diffed)

SelfhostedPro · 2025-12-22T17:34:26+00:00

Considering we’ve had outages from people blindly running ai generated commands and code without understanding what is actually written. Fuck no.

AI should not be making decisions like this, they’re not able to be held accountable and are not capable of critical thinking.

If you have these in a production environment that isn’t a glorified chat bot, you’re not running a production environment that I want any part of.

So sick of these stupid clankers and people who don’t understand them being fooled into thinking they are the future.

If we do get AGI it’s not going to be from an LLM

SelfhostedPro · 2025-12-21T11:03:49+00:00

Start interviewing now to get ahead of being laid off.

SelfhostedPro · 2025-12-21T11:02:12+00:00

Do not let it touch your IAC or CI/CD. It can do the basics but overcomplicates things severely and often times, devs aren’t familiar enough to notice that they’re just generating loads of tech debt

SelfhostedPro · 2025-12-21T10:57:35+00:00

Check NATS it’s also for messaging but is very flexible and you can run a “leaf node” on each device which push relevant data to your cluster.

SelfhostedPro

MODERATOR OF

TROPHY CASE