4 ms·
Ok, I'll bite. We (mergent.co) have looked at similar tools before but ended up managing our own infra. This is primarily because the tools we've found focus on
by jamescmartinez 3y ago
Ok, I'll bite. We (mergent.co) have looked at similar tools before but ended up managing our own infra. This is primarily because the tools we've found focus on recreating Heroku/similar on our AWS, which doesn't suit our needs.
For example, in addition to traditional applications, we run:
- Kubernetes + Knative
- Apache Pulsar
- ScyllaDB
- Elastic
- Clickhouse (soon)
How would Argonaut help us with our (frankly, painful) infra? We're living in YAML hell over here.
- suryao 3y agoThis type of use case leverages Argonaut's flexibility maximally. For traditional apps, the push-to-deploy CI/CD can be setup. For Pulsar and ScyllaDB, and Elastic there are helm charts that can be used very easily as a part of our AddOns which we are expanding continuously. For Knative and clickhouse, the best way to run them would be through Kubernetes operators. While this can be setup using Argonaut today, the experience feels janky and we're working on making this a first class entity in the product. The way Argonaut would help is by managing the configs and deployments in one place for easy collaboration and deployment, across environments and having GitOps with secret management for all the configs.
- deleted 3y ago[deleted]