Previously evaluated

Applications or solutions we have previously considered or work with

This document is for any evaluations of software or solutions we have done, why we've stopped using it (or put it on hold) and what experience we got from them.

KubeApps

We used to use KubeApps and still use it for our old cluster, however we're migrating away from it since the new major release (v2) made the solution much more unstable. We're also switching to decleratively defining our whole infrastructure through GitOps and other tools.

ArrangoCD

When we decided to go over to fully decleared cluster instead of using KubeApps, we considered Arrangocd vs. Flux. We wanted a primarily automated system, with Git being the primary tool to handle cluster state. We already had experience using Flux in other projects and had completed a symbiotic setup of other tools with Flux's image automation, alerts and recievers to automate releases, version management and more. That in addition to it being possible to run Arrangocd and Flux side-by-side made us choose Flux for our cluster.

DigitalOcean Managed Kubernetes

We are currently migrating away from managed kubernetes due to cost vs. running Talos. DO also has a low PVC limit which added a lot of overhead in having to run a lot of nodes for a small amount of workloads that needed PVC's.

Seaweedfs

We had Seaweedfs working for a few weeks but ended up with a bug, most likely due to a bug in the local storage provider CSI.

Longhorn CSI

We have people internally that has worked in companies which uses longhorn, the experience was that it required a lot more maintainance than it should. So we decided to go with other options.

Infrastructure Apps

Applications that are critical or important for our infrastructure

Bootstrapping a new cluster

Steps for setting up a cluster