2 ms·
Hi Philip, have been following GlassKube and Distr for a while. Have you considered the perspective that this could be used for internal deployments of product
by kungfufrog 8mo ago
Hi Philip, have been following GlassKube and Distr for a while.
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.
- pmig 8mo agoThanks for sticking around! Yes indeed, Distr already has a lot of features and can replace many other tools in your deployment stack (e.g., CI, log collection, alerts, licensing, secrets, OCI registry, customer & user management). Users definitely also use us for internal deployments, but there are some trade-offs you’ll need to make compared to the zero-config setup you get when deploying your Next.js app to Vercel on the one hand, and the hardcore customization you get when running your own GitOps/Terraform setup on the other. Is there any specific feature you’re missing, or is it just that our website doesn’t really highlight that use case?
- kungfufrog 8mo agoI think with the OpenTofu / Terraform support you're very close to enabling patterns that platform teams typically look for. 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!
- pmig 8mo agoNice to hear, feel free to leave any feedback while exploring Distr.