3 ms·

Very cool! I’ve been fiddling with terraform, ec2 + microk8s, eks, rancher fleet and crossplane over the weekend, trying to set up infra for a novel key-value s

Very cool! I’ve been fiddling with terraform, ec2 + microk8s, eks, rancher fleet and crossplane over the weekend, trying to set up infra for a novel key-value store I’m working on. But there sure are a lot of ways to screw this up and get bogged down in devops work, instead of building product. My only concerns would be: 1) do I have a realistic “exit strategy” or am I de facto locked into your platform and 2) as an old school engineer I don’t feel fully comfortable with a click-ops platform, unless it can generate terraform or similar.

suryao 3y ago
This is a concern we hear often. We have taken some steps to ensure that we do right by users in case users want an exit. Firstly, we use broadly adopted projects like ArgoCD for GitOps for apps and terraform for infra under the hood, though the tf is not exposed right now. All your config is in standard formats and can be transferred over. We are working on exposing these natively (and securely). You would be losing "push to deploy" CI pipelines though, since that requires hosted infra and workflow management that is actively done by Argonaut. Hope that answers your question.