kurtosis VS argo-cd

100%. Containers are essentially the new language-agnostic software libraries, but our current tools aren't adapted to write and distribute the "programs" formed from gluing them together.

(Mostly-shameless plug, this is what we're trying to solve with Kurtosis: https://github.com/kurtosis-tech/kurtosis )

We're trying to do this at Kurtosis! (https://github.com/kurtosis-tech/kurtosis)

The idea is to write your environment in Starlark (a minimal Python subset) and we'll handle running it on Docker or Kubernetes for you.

We started with "reduce Kubernetes complexity" so we don't yet have the full Kubernetes ejection seat, but we're slowly marching towards it - feedback welcome!

Hey djupblue, right here! https://github.com/kurtosis-tech/kurtosis/#:~:text=Check%20o...

I'm building a Starlark-based build system that operates at the level of building multi-container environments, rather than normal code assets: https://github.com/kurtosis-tech/kurtosis

It's kind of like Docker in the sense that it packages up an application in a reproducible, composable, and portable way...but instead of working at the level of one server, it works at the level of multi-server applications.

In the back of my head I'm very curious about making an application that just messages me on WhatsApp whenever its the birthday of one of my close friends because I never remember those

We are source available under the BSL license at - https://github.com/kurtosis-tech/kurtosis

Here are our docs: https://docs.kurtosis.com/. I'm happy to answer any questions :)

Hello HN!

We’re Kevin and Galen, the co-founders of Kurtosis.

Kurtosis is a composable build system for multi-container test environments. The goal is to make it easier for developers to set up test environments that require dynamic setup logic (e.g. passing IPs or runtime-generated data between services) or programmatic data seeding.

Right now, people usually define these multi-container test environments with scripting languages like Bash or Python atop Docker or Kubernetes. This can be very fragile, and difficult to share. We set out to build a tool that provides first-class parameterizability, composability, and safety so it’s easy to reuse and recombine the environment definitions across tests.

Kurtosis' runtime also abstracts the underlying container orchestrator, so test environments will run the same way whether they’re on a laptop or in a CI system, Docker or Kubernetes.

We’d love to hear your thoughts and feedback on what we’ve built. And if you find yourself facing the problems we set out to solve, we’d love to hear how we can make Kurtosis more useful for you!

Repo: https://github.com/kurtosis-tech/kurtosis/

The code above will create the argocd Kubernetes namespace and deploy the latest stable manifest. If you would like to install a specific manifest, have a look here.

In this blog post, we will demonstrate how easy and fast it is to deploy Sveltos on an RKE2 cluster with the help of ArgoCD, register two RKE2 Cluster API (CAPI) clusters and create a ClusterProfile to deploy Prometheus and Grafana Helm charts down the managed CAPI clusters.

Argo CD

$version = (Invoke-RestMethod https://api.github.com/repos/argoproj/argo-cd/releases/latest).tag_name Invoke-WebRequest -Uri "https://github.com/argoproj/argo-cd/releases/download/$version/argocd-windows-amd64.exe" -OutFile "argocd.exe"

This is cool - I can think of some projects that are amazing as first contributors, and others I can think of that are terrible.

One thing I think the tool doesn't address is why someone should contribute to a particular project. Having stars is interesting, and a proxy for at least historical activity, but also kind of useless here - take argoproj/argo-cd [1] as an example - 14.5k stars, with a backlog of 2.7k issues and an issue tracker that's a real mess.

Either way, I think this tool is neat for trying to gain some experience in a project purely based on language.

[1] https://github.com/argoproj/argo-cd/issues?q=is%3Aissue+is%3...

In our case, our team went ahead with Solution B, as that was the only solution present when the issue occurred. However, with the release of Argo CD 2.8.0 (released on August 7, 2023), things have changed - for the better :). Now, there are two ways to handle the sharding issue with the Argo CD Application Controller:

$ kubectl create namespace argocd //Next, let's apply the yaml configuration files for ArgoCd $ kubectl apply -n argocd -f https://raw.githubusercontent.com/argoproj/argo-cd/stable/manifests/install.yaml //Now we can view the pods created in the ArgoCD namespace. $ kubectl get pods -n argocd //To interact with the API Server we need to deploy the CLI: $ curl --silent --location -o /usr/local/bin/argocd https://github.com/argoproj/argo-cd/releases/download/v2.4.7/argocd-linux-amd64 $ chmod +x /usr/local/bin/argocd //Expose argocd-server $ kubectl patch svc argocd-server -n argocd -p '{"spec": {"type": "LoadBalancer"}}' //Wait about 2 minutes for the LoadBalancer creation $ kubectl get svc -n argocd //Get pasword and decode it. $ kubectl get secret argocd-initial-admin-secret -n argocd -o yaml $ echo WXVpLUg2LWxoWjRkSHFmSA== | base64 --decode

From here, we can explore other developments and tutorials on Kubernetes, such as o11y or observability (PLG, ELK, ELF, TICK, Jaeger, Pyroscope), service mesh (Linkerd, Istio, NSM, Consul Connect, Cillium), and progressive delivery (ArgoCD, FluxCD, Spinnaker).

lol! Wham! Third choice! https://github.com/argoproj/argo-cd

If you mean for each app, I don't think it's listed anywhere though you may find it in `repo-server` logs. Like so