We migrated onto K8s in less than 12 months

• Nomad

  104 14,760 9.9 Go

  Nomad is an easy-to-use, flexible, and performant workload orchestrator that can deploy a mix of microservice, batch, containerized, and non-containerized applications. Nomad is easy to operate and scale and has native Consul and Vault integrations.

  

• InfluxDB

  www.influxdata.com featured

  Purpose built for real-time analytics at any scale. InfluxDB Platform is powered by columnar analytics, optimized for cost-efficient storage, and built with open data standards.

  

• modelpad

  1 5 9.0 TypeScript

  Even on a small project it's actually better imo than tying everything to a platform like netlify or vercel. I have this little notepad app that I deploy to a two node cluster in a github action and its an excellent workflow. The k8s to get everything deployed, provision tls and everything is like 50 lines of yaml, I could pretty easily make it support branch previews or whatever too. https://github.com/SteveCastle/modelpad

• kubernetes

  708 109,628 10.0 Go

  Production-Grade Container Scheduling and Management

  

  If you start using more esoteric features the reliability of k8s goes down. Guess what happens when you enable the in place vertical pod scaling feature gate?

  It restarts every single container in the cluster at the same time: https://github.com/kubernetes/kubernetes/issues/122028

  We have also found data races in the statefulset controller which only occurs when you have thousands of statefulsets.

  Overall, if you stay on the beaten path k8s reliability is good.

• helm-unittest

  1 786 9.4 Go

  BDD styled unit test framework for Kubernetes Helm charts as a Helm plugin. (by helm-unittest)

  

  Whilst I'll agree that writing helm charts isn't particularly delightful, consuming them can be.

  In our case we have a single application/service base helm chart that provides sane defaults and all our deployments extend from. The amount of helm values config required by the consumers is minimal, and there has been very little occasion for a consumer to include their own templates - the base chart exposes enough knobs to avoid this.

  When it comes to third-party charts, many we've been able to deploy as is (sometimes with some PRs upstream to add extra functionality), and occasionally we've needed to wrap/fork them. We've deployed far more third-party charts as-is than not though.

  One thing probably worth mentioning w.r.t to maintaining our custom charts is the use of helm unittest (https://github.com/helm-unittest/helm-unittest) - it's been a big help to avoid regressions.

  We do manage a few kubernetes resources through terraform, including Argocd (via the helm provider which is rather slow when you have a lot of CRDs), but generally we've found helm chart deployed through Argocd to be much more manageable and productive.

• timoni

  13 1,503 9.2 Go

  Timoni is a package manager for Kubernetes, powered by CUE and inspired by Helm.

• SaaSHub

  www.saashub.com featured

  SaaSHub - Software Alternatives and Reviews. SaaSHub helps you find the best software and product alternatives

  

Suggest a related project