helm-charts
Helm Charts published by Bedag Informatik AG (by bedag)
grafana-delivery
Kustomization files for deploying grafana into K8S cluster (by nikita-akuity)
| helm-charts | grafana-delivery | |
|---|---|---|
| 2 | 1 | |
| 25 | 6 | |
| - | - | |
| 7.3 | 10.0 | |
| 15 days ago | over 1 year ago | |
| Smarty | Shell | |
| Apache License 2.0 | - |
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.
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.
helm-charts
Posts with mentions or reviews of helm-charts.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-12-03.
-
GKE with Consul Service Mesh
repositories: # https://artifacthub.io/packages/helm/dgraph/dgraph/0.0.19 - name: dgraph url: https://charts.dgraph.io # https://artifacthub.io/packages/helm/main/raw - name: bedag url: https://bedag.github.io/helm-charts/ releases: # Dgraph additional resources required to support Consul - name: dgraph-extra chart: bedag/raw namespace: dgraph version: 1.1.0 values: - resources: - apiVersion: v1 kind: ServiceAccount metadata: name: dgraph-dgraph-zero - apiVersion: v1 kind: ServiceAccount metadata: name: dgraph-dgraph-alpha - apiVersion: v1 kind: ServiceAccount metadata: name: dgraph-dgraph-alpha-grpc - apiVersion: v1 kind: Service metadata: name: dgraph-dgraph-alpha-grpc spec: ports: - name: grpc-alpha port: 9080 publishNotReadyAddresses: true selector: app: dgraph chart: dgraph-0.0.19 component: alpha release: dgraph type: ClusterIP # Dgraph cluster with 2 x StatefulSet (3 Zero pods, 3 Alpha pods) - name: dgraph namespace: dgraph chart: dgraph/dgraph version: 0.0.19 needs: - dgraph/dgraph-extra values: - image: tag: v21.03.2 zero: extraAnnotations: consul.hashicorp.com/connect-inject: 'true' # disable transparent-proxy for multi-port services consul.hashicorp.com/transparent-proxy: 'false' consul.hashicorp.com/transparent-proxy-exclude-inbound-ports: "5080,7080" consul.hashicorp.com/transparent-proxy-exclude-outbound-ports: "5080,7080" alpha: extraAnnotations: consul.hashicorp.com/connect-inject: 'true' # disable transparent-proxy for multi-port services consul.hashicorp.com/transparent-proxy: 'false' # use these registered consul services for different ports consul.hashicorp.com/connect-service: 'dgraph-dgraph-alpha,dgraph-dgraph-alpha-grpc' consul.hashicorp.com/connect-service-port: '8080,9080' consul.hashicorp.com/transparent-proxy-exclude-inbound-ports: "5080,7080" consul.hashicorp.com/transparent-proxy-exclude-outbound-ports: "5080,7080" configFile: config.yaml: | security: whitelist: {{ env "DG_ACCEPT_LIST" | default "0.0.0.0/0" | quote }} # patch existing resources using merge patches strategicMergePatches: # add serviceAccountName to Alpha StatefulSet - apiVersion: apps/v1 kind: StatefulSet metadata: name: dgraph-dgraph-alpha spec: template: spec: serviceAccountName: dgraph-dgraph-alpha # add serviceAccountName to Zero StatefulSet - apiVersion: apps/v1 kind: StatefulSet metadata: name: dgraph-dgraph-zero spec: template: spec: serviceAccountName: dgraph-dgraph-zero # add label to Alpha headless service - apiVersion: v1 kind: Service metadata: name: dgraph-dgraph-alpha-headless labels: consul.hashicorp.com/service-ignore: 'true' # add label to Zero headless service - apiVersion: v1 kind: Service metadata: name: dgraph-dgraph-zero-headless labels: consul.hashicorp.com/service-ignore: 'true' # patch existing resource using jsonPatches jsonPatches: # remove existing grpc port from serivce - target: version: v1 kind: Service name: dgraph-dgraph-alpha patch: - op: remove path: /spec/ports/1
-
How are charts & manifests usually deployed together?
https://github.com/helmfile/helmfile + incubator raw
grafana-delivery
Posts with mentions or reviews of grafana-delivery.
We have used some of these posts to build our list of alternatives
and similar projects. The last one was on 2022-09-25.
What are some alternatives?
When comparing helm-charts and grafana-delivery you can also consider the following projects:
google.cloud - GCP Ansible Collection https://galaxy.ansible.com/google/cloud
helmfile - Declaratively deploy your Kubernetes manifests, Kustomize configs, and Charts as Helm releases. Generate all-in-one manifests for use with ArgoCD.
hub-feedback - Feedback and bug reports for the Docker Hub
envoy - Cloud-native high-performance edge/middle/service proxy
consul-k8s-ingress-controllers - Testing for different API gateways with Consul
ratel - Dgraph Data Visualizer and Cluster Manager
istio - Connect, secure, control, and observe services.
consul-k8s - First-class support for Consul Service Mesh on Kubernetes
pydgraph-client - Demonstraiton Dgraph client that using pydrgraph library
traefik-consul
zsh - Mirror of the Z shell source code repository.
helm - The Kubernetes Package Manager
helm-charts vs google.cloud
helm-charts vs helmfile
helm-charts vs hub-feedback
helm-charts vs envoy
helm-charts vs consul-k8s-ingress-controllers
helm-charts vs ratel
helm-charts vs istio
helm-charts vs consul-k8s
helm-charts vs pydgraph-client
helm-charts vs traefik-consul
helm-charts vs zsh
helm-charts vs helm