charts
DISCONTINUED
helm-charts
Our great sponsors
charts | helm-charts | |
---|---|---|
25 | 7 | |
15,373 | 443 | |
- | 3.6% | |
2.1 | 7.6 | |
about 1 year ago | 5 days ago | |
Go | Mustache | |
Apache License 2.0 | 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.
charts
-
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
-
How to silence Prometheus Alertmanager using config files?
I'm using the official stable/prometheus-operator chart do deploy Prometheus with helm.
-
Prometheus Definitive Guide Part III - Prometheus Operator
Enter the default username: admin and password: prom-operator which you can find from here to access Grafana.
- Multipass, Microk8s, Prometheus and Grafana
- ECS migrate to EKS part 3
-
Deploying Jenkins on Google Cloud
In this step opta generates terraform code to deploys helm chart. You can review the plan and accept it. It will take around 2-3 minutes for the plan to get applied. For specifying values to the helm chart you can modify the values inside opta-gcp/opta.yml . Refer to jenkins helm chart for more details https://github.com/helm/charts/tree/master/stable/jenkins. After opta apply finishes you will have jenkins up and running on your infra.
-
k8s-secretgen: Got tired of generating secrets for testing stuff so I made a script to automate it.
I do use Helm to deploy, but the trouble with using it for secrets is that it overwrites them on an upgrade.
-
My Journey With Spark On Kubernetes... In Python (1/3)
In this section, you use Helm to deploy the Kubernetes Operator for Apache Spark from the incubator Chart repository. Helm is a package manager you can use to configure and deploy Kubernetes apps.
-
Autoscaling Redis applications on Kubernetes 🚀🚀
Redis: I have used Azure Cache for Redis, but feel free to explore other options e.g. you can install one in your Kubernetes cluster using a Helm chart).
-
How to Monitor your Azure Kubernetes Cluster
To install Prometheus, the most convenient way is using the Prometheus Operator Helm Chart. Helm is a package manager for Kubernetes. It simplifies the installation by integrating most of the necessary configuration settings into one package. The following instructions are based on a blog post which describes the installation process specific for AKS clusters.
helm-charts
- Deploying Jenkins on Google Cloud
-
Jenkins on Kubernetes - Can't Use PodTemplates Defined In Clouds
I am settings up a Jenkins instance in Kubernetes using the Helm Chart and I'm stuck with agents.
I've updated my post with the error logs and some descriptions. The "Additional Agents" thing is part of the Helm chart. The Adding Pod Templates Using additionalAgents section of the Helm Chart's README gives an example of how to declare them. I initially tried using a direct copy of the example in the README (adapted to use with the Ansible module) but that displayed roughly the same behaviour
-
Should we be using Jenkins for our Kubernetes CI/CD pipeline needs in 2021?
https://github.com/jenkinsci/helm-charts/tree/main/charts/jenkins Using offical chart
- Battle-tested way to configure a Jenkins server on AWS using IaC/CaC?
What are some alternatives?
actions-runner-controller - Kubernetes controller for GitHub Actions self-hosted runners
kubernetes-mixin - A set of Grafana dashboards and Prometheus alerts for Kubernetes.
kubernetes-operator - Kubernetes native Jenkins Operator
external-dns - Configure external DNS servers (AWS Route53, Google CloudDNS and others) for Kubernetes Ingresses and Services
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
volcano - A Cloud Native Batch System (Project under CNCF)
kube-state-metrics - Add-on agent to generate and expose cluster-level metrics.
spark-on-k8s-operator - Kubernetes operator for managing the lifecycle of Apache Spark applications on Kubernetes.
prometheus-operator - Prometheus Operator creates/configures/manages Prometheus clusters atop Kubernetes
metrics-server - Scalable and efficient source of container resource metrics for Kubernetes built-in autoscaling pipelines.
helm-diff - A helm plugin that shows a diff explaining what a helm upgrade would change