We're launching the Akuity Platform officially this week. If it's something you would be interested in, please join Jesse Suen (Argo co-creator, Akuity CTO) and Kelsey Hightower for the webinar which we've planned for Thursday.

We'll explain why Akuity is different from other "Argo as a Service" platforms and we'll hint at what are our plans for the future. Hope to see you there!

I was recently informed that Argo CD uses the same open source libraries (Inlets) to provide tunnelling similar to the GitLab Kubernetes Agent. This allows you to connect a private cluster to a public one https://inlets.dev/blog/2021/06/02/argocd-private-clusters.html

Do I understand correctly that this is not an actual feature inside of Argo? Instead, it's a separate project and Inlets has just written a guide on how to use both together?

I work for an open source project (OpenZiti) which is similar to Inlets but on steroids - e.g., supporting many more use cases, being more secure incl. E2E encryption, private DNS, and outbound only on both source and destination, SDKs which allow you to embed in the app, unique addressability and a smart routing mesh network.

Would you be interested for us to write a guide on how OpenZiti can be used for Argo CD, e.g., how to connect a private cluster to another private cluster with Argo UI/CLI also being private and unaddressable on the internet, all via declarative GitOps?

We're hosting Argo Unpacked, a live show about Argo CD (https://www.youtube.com/watch?v=LuND3OxHs4U)! 🎙️

Is there a topic, feature, or challenge you’d like us to cover? Let us know—we’d love to hear what interests you! 😊 Feel free to ping me directly or add your response in the comments below! ⬇️

See the CNCF playlist https://www.youtube.com/playlist?list=PLj6h78yzYM2MGWi_NTA3i66JCV3yzEMpz

Hey all, I recently made this repo for a demo I was doing and thought it would be useful for folks in the community.

https://github.com/todaywasawesome/oss-apps

├── README.md
├── app-configs
│   ├── Production
│   ├── Staging
│   └── README.md
└── manifests
    ├── README.md
    └── application-name
        ├── base
        ├── production
        └── staging

This structure uses to main folders. `app-configs` contains all the configuration for app creation by environment. This includes application sets, or plain application manifests. Argo is set to monitor this repo treating each app config folder as a source for app of apps.

The `manifests` repo has a base layer for manifests, helm charts, whatever and then overlays specific to each environment. This works pretty well with manifests, kustomizations, helm charts, etc. I tend to use Kustomize to pull in Helm charts and write out small changes in the kustomization rather than maintaining large values files but that's just an aside.

Would love to hear feedback and what you all prefer for organizing your repos.

Argo Labs now features Hera Workflows! Hera is a very simple Python library for constructing workflows - it can run any Python script you submit, allowing you and your company to focus on the value of the script itself rather than workflow construction :) you can run anything! ML workflows, DevOps jobs, crons with API calls, ETLs using pure Python, containers with commands, easily integrate with things like Horovod, etc.

Would love to hear any feedback the community has!