kubernetes-operator-roiergasias
Orkestra
| kubernetes-operator-roiergasias | Orkestra | |
|---|---|---|
| 1 | 4 | |
| 7 | 102 | |
| - | 0.0% | |
| 4.8 | 0.0 | |
| almost 3 years ago | about 1 year ago | |
| Go | Go | |
| GNU General Public License v3.0 only | GNU General Public License v3.0 or later |
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.
kubernetes-operator-roiergasias
Orkestra
-
Managing lifecycle of a (complex) group of helm applications with Azure Orkestra
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
-
Orchestration and lifecycle management for complex applications on Kubernetes
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
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?
flyte - Scalable and flexible workflow orchestration platform that seamlessly unifies data, ML and analytics stacks.
argo - Workflow Engine for Kubernetes
helm-s3 - ⎈ Helm plugin that adds support for AWS S3 as a chart repository.
charts - ⚠️(OBSOLETE) Curated applications for Kubernetes
nifikop - The NiFiKop NiFi Kubernetes operator makes it easy to run Apache NiFi on Kubernetes. Apache NiFI is a free, open-source solution that support powerful and scalable directed graphs of data routing, transformation, and system mediation logic.
argo-cd - Declarative Continuous Deployment for Kubernetes
volcano - A Cloud Native Batch System (Project under CNCF)
Flux - Successor: https://github.com/fluxcd/flux2
csi-s3 - A Container Storage Interface for S3
keel - Kubernetes Operator to automate Helm, DaemonSet, StatefulSet & Deployment updates
onepanel - The open source, end-to-end computer vision platform. Label, build, train, tune, deploy and automate in a unified platform that runs on any cloud and on-premises.
runbooks - Finetune LLMs on K8s by using Runbooks