charts VS Orkestra

Compare charts vs Orkestra and see what are their differences.

charts

⚠️(OBSOLETE) Curated applications for Kubernetes (by helm)

Orkestra

Orkestra is a cloud-native release orchestration and lifecycle management (LCM) platform for the fine-grained orchestration of inter-dependent helm charts and their dependencies (by Azure)
Our great sponsors
  • OPS - Build and Run Open Source Unikernels
  • Scout APM - Less time debugging, more time building
  • SonarLint - Deliver Cleaner and Safer Code - Right in Your IDE of Choice!
charts Orkestra
14 4
15,345 72
0.2% -
2.5 8.8
10 days ago 2 months ago
Go Go
Apache License 2.0 GNU General Public License v3.0 or later
The number of mentions indicates the total number of mentions that we've tracked plus the number of user suggested alternatives.
Stars - the number of stars that a project has on GitHub. Growth - month over month growth in stars.
Activity is a relative number indicating how actively a project is being developed. Recent commits have higher weight than older ones.
For example, an activity of 9.0 indicates that a project is amongst the top 10% of the most actively developed projects that we are tracking.

charts

Posts with mentions or reviews of charts. We have used some of these posts to build our list of alternatives and similar projects. The last one was on 2021-09-21.

Orkestra

Posts with mentions or reviews of Orkestra. We have used some of these posts to build our list of alternatives and similar projects.
  • Managing lifecycle of a (complex) group of helm applications with Azure Orkestra
    1 project | reddit.com/r/kubernetes | 20 Sep 2021
    Github Repo - Azure/orkestra: Orkestra is a cloud-native release orchestration and lifecycle management (LCM) platform for the fine-grained orchestration of inter-dependent helm charts and their dependencies (github.com)
  • Orkestra helps you orchestrate your complex helm releases and manage the lifecycle of your applications by carrying out "non-disruptive" in-service upgrade
    1 project | reddit.com/r/kubernetes | 26 Apr 2021
  • Orchestration and lifecycle management for complex applications on Kubernetes
    1 project | news.ycombinator.com | 23 Mar 2021
    Orchestration of a group of complex applications with dependencies between themselves and their subcharts/dependencies is hard

    Imagine a scenario in which application that depends on Prometheus, Grafana and Istio. Now let's take it a step further and define a dependency between Istio and it's observability components, Prometheus & Grafana, since Istio itself leverages both Prometheus and Grafana for it's control-plane. In other words we now have a dependency DAG where, the application depends-on Istio depends-on Prometheus & Grafana. Now imagine the application depending on other applications that provide PaaS like infrastructure capabilities required to run the application itself

    Defining this dependency order allows all components to spin up both, reliably and efficiently

    This would make a huge difference when we are dealing with complex applications like 5G network functions running mission-critical workloads across the network and their lifecycle management (installs/upgrades/rollback). Providers, tend to take releases in a "semi-continuous" manner as opposed to true CD. Meaning, when upgrading, multiple applications and their subcharts may be upgraded in a single release. This is a scenario in which defining the dependency ordering between the applications and their subcharts allows the service providers to limit the blast radius if this go wrong, allowing them to fail fast and rollback without impacting all upgrade-ready apps

    Introducing Azure Orkestra https://github.com/Azure/Orkestra that provides the aforementioned capabilities using a familiar Kubernetes declarative CRDscalled ApplicationGroups. Orkestra leverages Argo Workflows to generate DAG workflows to deploy all applications with an application group (and optionally a DAG workflow for the subcharts in each application). The DAG on execution generates HelmRelease objects that are then acted upon by flux helm-operator to reliably perform the helm actions (install, delete, upgrade, rollback)

  • Orchestrate complex, mission-critical applications with Azure/Orkestra
    1 project | reddit.com/r/kubernetes | 23 Mar 2021
    Introducing Azure Orkestra https://github.com/Azure/Orkestra that provides the aforementioned capabilities and features using familiar Kubernetes declarative objects (CRDs) called ApplicationGroups.

What are some alternatives?

When comparing charts and Orkestra you can also consider the following projects:

external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services

argo - Workflow engine for Kubernetes

cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming [Moved to: https://github.com/cdk8s-team/cdk8s]

keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes

kubernetes-mixin - A set of Grafana dashboards and Prometheus alerts for Kubernetes.

volcano - A Cloud Native Batch System (Project under CNCF)

prometheus-operator - Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes

kube-state-metrics - Add-on agent to generate and expose cluster-level metrics.

virtual-kubelet - Virtual Kubelet is an open source Kubernetes kubelet implementation.

Resque - Resque is a Redis-backed Ruby library for creating background jobs, placing them on multiple queues, and processing them later.

go-echarts - 🎨 The adorable charts library for Golang

argo-cd - Declarative continuous deployment for Kubernetes.