Hacker News Board Hacker News, browsed like a classic message board
Live data from Hacker News

Kargo, a multi-stage application lifecycle orchestrator

akuity.io

Post reply on HN
Print view View original

31–40 of 83 posts

Re: Kargo, a multi-stage application lifecycle orchestrator

#31

Post by greatfood230 »

candiddevmike wrote: post #26
rjzzleep wrote: post #18

I've used Flux, Flux2 and Argo for GitOps, and they all had their quirks. In general it seems that most CloudNative projects were kinda set in their own vision with very opinionated devs and a lot of corner cases that are not accounted for and won't be accounted for. I have a little bit of hope that this one is going to be different with the lessons they got from Argo, but I'm not holding my breath. Ps. when I first…

Akuity is getting their lunch eaten by Harness and need some kind of IP to sell besides Argo-as-a-Service. I don't really see a path forward for them in the very crowded CI/CD space, so I would wait to see how they will monetize this and who the first movers are before attempting to use it. From a business standpoint, Akuity had their Series A in 2022 and raised $25M. They have yet to show up on anyone's radar, IMO.…

There is enough space for innovation for tools. Harness product is stretched thin and trying to do everything like throwing Pizzas to the wall to check if it sticks in order to boost the valuation. I doubt it will do everything well and make sense to all the users.

Re: Kargo, a multi-stage application lifecycle orchestrator

#32

Post by nickjj »

therealkrancour wrote: post #30
nickjj wrote: post #24

Earlier quoted context omitted.

> With _just_ Kustomize and Argo CD, those changes roll out to all environments all at once. With Kargo, you can progress the change and (re-)validate it environment-by-environment. In prod it wouldn't get rolled out until someone manually clicks the sync button for each app in that environment. But yes, in staging it would get AutoSync'd to all of the apps. I get what you're saying though. It will be curious to see…

> In prod it wouldn't get rolled out until someone manually clicks the sync button That's a great point and if that works for you, awesome! Note though that relies on the state of the prod Application to temporarily contradict the source of truth that is your repo. If you lose that prod Application and re-create it, prod will be in a state you hadn't yet blessed.

Indeed. That use case hasn't been something I encountered yet since we generally operate at a scale where our apps at the Argo CD level rarely change once they've been created.

But thanks for pointing out the mismatch on the source of truth. Definitely something to consider.

Re: Kargo, a multi-stage application lifecycle orchestrator

#33

Post by sleepybrett »

abuckenheimer wrote: post #19

I've only skimmed the quickstart docs https://kargo.akuity.io/quickstart/ but this snippet immediately clicks for me as something that I'd want to try cat Have enjoyed using argo in general in the past, its got a great model for k8s native workflows / events but never got to using it for CD.

Yeah we use argo workflows to power some e2e testing and rollouts for canary blue/green, and their notification server, but don't actually use their cd product.

Re: Kargo, a multi-stage application lifecycle orchestrator

#35

Post by what-no-tests »

ThinkBeat wrote: post #29

I can almost follow this but I am at the edge of where I see how it could sound like buzzword gibberish. I dont blame the author(s) but things are getting more specialized and more terms are created. (which usually maps to an existing term which also maps to an existed term which also maps an existing term and so on. I have though about trying to create a "terminator"(hah) where you can paste in something from a new…

Weird thing is, when I read that quote it makes perfect sense.

But I understand how it could look like the undecoded bytefall in the Matrix for those outside the know.

Re: Kargo, a multi-stage application lifecycle orchestrator

#36

Post by jmorenoamor »

bingemaker wrote: post #8

Is this tool similar to https://dagger.io/ ?

Wow, looks interesting.

You make per project makefile-like python pipelines that are executed by an installed runtime/docker container?

Then I will give it a try, I've been looking for a lightweight local ad-hoc jenkins substitute.

Re: Kargo, a multi-stage application lifecycle orchestrator

#39

Post by AaronM »

robertlagrant wrote: post #38

Every time there's a new tool, it's worth considering if it locks in previous choices. E.g. ArgoCD means I can't move off Kubernetes. Will Kargo mean I can't move off ArgoCD or Kubernetes?

Using Kubernetes locks you into kubernetes. ArgoCD doesn't lock you into Kubernetes because its just a wrapper around managing kubernetes manifests

Its like arguing that cloudformation locks you into aws

Re: Kargo, a multi-stage application lifecycle orchestrator

#40

Post by k8svet »

Another project announcement, another situation where I would literally pay a coffee's worth to cut to the chase -- why is there a need for another GitOps tool when several already exist?

Tighter integration with other Argo products? Why is this not simple a new component of Argo CI/CD? How much is "thought-leadership" a part of it, it is Kubernetes-adjacent, after all.

So far even the answers in this thread leaving me asking these questions even more strongly? If Argo CD is a "continuous deployment" tool, why isn't the priority making staged-rollouts a first class feature in Argo CD itself?

This is coming from a place of curiosity, not simply being a miser, I promise.

Post reply on HN