GitHub user marcusaram added a comment to the discussion: 📢 CloudStack Kubernetes Flavors — A Reference Guide I Wish I Had When I Started
We evaluated Omni when Sidero Labs stopped working on the Talos CAPI provider and put their effort into Omni. It still wasn't what we were looking for. Pricing was part of it, but mainly we wanted full self service with fully automated provisioning, inside our own customer portal. Our portal started out in PHP (Laravel), which didn't always run smoothly. So we rewrote it in Go and made it more generic along the way, and it's now becoming a product of its own (shameless self-promotion: [Nubriva](https://nubriva.com/)). At a high level, the stack is: Core: a Go application that handles customers, ordering, billing and the panels. Plugins: separate Go plugins. Each integration is a plugin: CloudStack, Talos, DNS, accounting, and so on. Frontend: Vue. Talos/Kubernetes: the plugin talks to the Talos API directly through Sidero's Go machinery library, no talosctl. Add-ons go on with the Helm Go SDK and client-go, and CloudStack is driven through its API. That keeps the core generic: adding a new provider is "just" another plugin. And since most of the Kubernetes ecosystem is written in Go, we can use those tools directly as libraries instead of shelling out to their CLIs. GitHub link: https://github.com/apache/cloudstack/discussions/13638#discussioncomment-18829720 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected]
