This message was deleted.

started with GitLab and now planning to use Argo. The main reason is that we have to expose public internet loads. Which causes us to separate our code builds from our deployments.

Specifically deploying? Argo but buildkite commands do the git pushing which triggers the argo syncing to do the deploying

Homegrown tooling, which I’m currently trying to integrate with Argo

GitHub Actions for CI and Argo for CD.

Gitlab for now, OSS is a requirement for me but not necessarily for the companies I work for

we are using Argo (ArgoCD, Argo Image Updater, Argo Rollouts) + Kustomize (with some KRM functions, Jinja templating to automate stuff).

We are using Spinnaker (was created by Netflix). It serves us very well but it's a cannon and have much things to do and care about, maybe if we can start from 0 again someday Argo seems to be the reasonable choice

Same as @Felipe Schossler, we’re using Spinnaker with custom templating using jsonnet to generate our pipelines. For simple deploying, it’s definitely overkill. Running it yourself is also not easy, as it’s a beast. But there are some very powerful advanced setups you can make.

@yoo Are you using Argo CD or Argo Workflows or something else?

I am curious what you all use for your platform stack. maybe a different thread 😉

@Raquel Pau Fernandez Argo CD. In addition ApplicationSets and Image Updater.