Prompt: > The car wash where I want to wash my car is 50 metres away, should I walk or drive there?

Response: > Great question with a slightly ironic twist! Here's the thing: if you're going to a car wash, you'll need to drive your car there — that's kind of the whole point! You can't really wash your car if you walk there without it. > > That said, 50 metres is an incredibly short distance, so you could walk over first to check for queues or opening hours, then drive your car over when you're ready. But for the actual car wash visit, drive!

I thought it was fair to explain I wanted to wash my car there... people may have other reasons for walking to the car wash! Asking the question itself is a little insipid, and I think quite a few humans would also fail it on a first pass. I would at least hope they would say: "why are you asking me such a silly question!"

Centralised management -> create a landing zone -> deploy and configure software/infrastructure -> maintain and manage from a single pane of glass.

The truth is this is typically a long road to maturity and robustness if putting this whole stack together yourself.

I am curious to explore using Distr in this space!

Have you considered the perspective that this could be used for internal deployments of product as well to multiple clusters/environments?

It puts a lot of pieces together end to end that are missing from building a deployment system around the defaults ArgoCD etc. There's a substantial gap between ArgoCD and getting to automated CI/CD with multi cluster support etc.

I will trial it for a bit and if I like it will definitely subscribe. Have you considered adding some premium features to help justify the subscription?

Happy user for a few months now :)

My current experience is that once we started transition to SOC 2 compliance and brought in new processes everything crawled to a halt, we now have multiple layers of reviews and scheduling, and the bureaucratic process is followed at the cost of expediency and doing sensible things in a sensible way (i.e., everything must follow the process, no matter how trivial or significant.)

Though these days, OLM and the Quarkus operator SDK give you a completely viable alternative approach to Helm that enables you to express much more complex functionality and dependency relationships over the lifecycle of resources. An example would be doing a DB backup before upgrading to a new release etc. Obviously this power comes at a cost.