Orkestra
charts
Orkestra | charts | |
---|---|---|
4 | 28 | |
102 | 15,373 | |
0.0% | - | |
0.0 | 2.1 | |
about 1 year ago | about 2 years ago | |
Go | Go | |
GNU General Public License v3.0 or later | Apache License 2.0 |
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.
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.
charts
- Nginx ingress resource - Redirect from to www (SSL doesn't work)
-
Prometheus: Monitor all services without creating ServiceMonitor for each service?
I'm using this prometheus helm chart.
-
Loading Kibana dashboards using Metricbeat through HELM charts
I did this using the incubator/raw chart ( https://github.com/helm/charts/tree/master/incubator/raw ), by creating a k8s Job.
-
K8S - using Prometheus to monitor another prometheus instance in secure way
I've installed Prometheus operator 0.34 (which works as expected) on cluster A (main prom)Now I want to use the federation option,I mean collect metrics from other Prometheus which is located on other K8S cluster B
-
Customize helm chart from stable repository
So I am using the helm chart stable/traefik to deploy a reverse proxy to my cluster. I need to customise it beyond what is possible with the variables I can set for the template.
- Helm Test best practices
-
✅ Updated guide for MetalLB v0.13+ (CRDs, baby!) with Flux, incl goofy diagrams illustrating L3 vs L2 👍
It may be that we just migrated to Bitnami's chart when the old "stable" chart was deprecated
-
Helm delete release and clear associated storage
Edit: I'm using Postgresql Stable Chart version 5.3.10
-
How to silence Prometheus Alertmanager using config files?
I'm using the official stable/prometheus-operator chart do deploy Prometheus with helm.
-
Airflow scheduler fails to start with kubernetes executor
I am using using https://github.com/helm/charts/tree/master/stable/airflow helm chart and building v1.10.8 puckle/docker-airflow image with kubernetes installed on it and using that image in the helm chart,But I keep getting
What are some alternatives?
argo - Workflow Engine for Kubernetes
kubernetes-mixin - A set of Grafana dashboards and Prometheus alerts for Kubernetes.
argo-cd - Declarative Continuous Deployment for Kubernetes
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
kubernetes-operator-roiergasias - 'Roiergasias' kubernetes operator is meant to address a fundamental requirement of any data science / machine learning project running their pipelines on Kubernetes - which is to quickly provision a declarative data pipeline (on demand) for their various project needs using simple kubectl commands. Basically, implementing the concept of No Ops. The fundamental principle is to utilise best of docker, kubernetes and programming language features to run a workflow with minimal workflow definition syntax. It is a Go based workflow running on command line or Kubernetes with the help of a custom operator for a quick and automated data pipeline for your machine learning projects (a flavor of MLOps).
cdk8s - Define Kubernetes native apps and abstractions using object-oriented programming [Moved to: https://github.com/cdk8s-team/cdk8s]
Flux - Successor: https://github.com/fluxcd/flux2
keda - KEDA is a Kubernetes-based Event Driven Autoscaling component. It provides event driven scale for any container running in Kubernetes
volcano - A Cloud Native Batch System (Project under CNCF)
kube-state-metrics - Add-on agent to generate and expose cluster-level metrics.
spark-operator - Kubernetes operator for managing the lifecycle of Apache Spark applications on Kubernetes.
prometheus-operator - Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes