cass-operator
helm-charts
Our great sponsors
cass-operator | helm-charts | |
---|---|---|
3 | 98 | |
256 | 4,647 | |
1.2% | 2.8% | |
0.0 | 9.7 | |
4 months ago | 4 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.
cass-operator
-
Why a Cloud-Native Database Must Run on K8s
The K8ssandra project uses cass-operator to automate Cassandra operations. Cass-operator defines a “CassandraDatatcenter” custom resource (CRD) to represent each top-level failure domain of a Cassandra cluster. This builds a higher-level abstraction based on Stateful Sets and Persistent Volumes.
-
Requirements for running K8ssandra for development
Cass Operator : Kubernetes Operator for Apache Cassandra
-
The search for a cloud-native database
For example, the K8ssandra project uses cass-operator, which defines a Kubernetes custom resource (CRD) called “CassandraDatacenter” to describe the desired state of each top-level failure domain of a Cassandra cluster. This provides a level of abstraction higher than dealing with Stateful Sets or individual pods.
helm-charts
-
You get what you Measure: Understanding your applications health with Grafana, Loki and Prometheus
Prometheus can be deployed using the Prometheus Helm Chart. This helm chart contains a lot of features such as the already mentioned Push Gateway, Alert Manager and so on. For simplicity reasons of this tutorial I will not show all the Helm chart configuration but you can see a real example used by me here.
-
Multi-Cluster Prometheus: Scaling Metrics Across Kubernetes Clusters
Building upon Bartłomiej Płotka's insightful blog on Prometheus and its passthrough agent mode, this post dives into implementing multi-cluster Prometheus support. Notably, the official inclusion of support in the widely-used kube-prometheus-stack came with the release in July 2023, making it easier to extend Prometheus monitoring across clusters.
-
Hands On: Pull metrics into Kubernetes from anywhere and treat them generically with the Keptn Metrics Server
The first thing you'll need, of course, is at least one backend to store metrics. So install Prometheus now:
-
Kubernetes Ingress Visibility
For the request following, something like jeager https://www.jaegertracing.io/, because you are talking more about tracing than necessarily logging. For just monitoring, https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack would be the starting point, then it depends. Nginx gives metrics out of the box, then you can pull in the dashboard like https://grafana.com/grafana/dashboards/14314-kubernetes-nginx-ingress-controller-nextgen-devops-nirvana/ , or full metal with something like service mesh monitoring which would provably fulfil most of the requirements
-
Smart-Cash project -Adding monitoring to EKS using Prometheus operator
kube-prometheus-stack is a Helm chart that contains several components to monitor the Kubernetes cluster, along with Grafana dashboards Grafana Dashboards to visualize the data. This option will be used in this article.
-
K8s Monitoring Per Namespace
This one I highly recommend: https://github.com/prometheus-community/helm-charts/tree/main/charts/kube-prometheus-stack
- Is Prometheus the right tool for my use case here?
-
Do we have any Prometheus metric to get the kubernetes cluster-level CPU/Memory requests/limits?
We use kube-prometheus-stack for metrics and have added the K8s views dashboards from grafana-dashboards-kubernetes. You should check out the k8s-views-global dashboard. I believe it's just what you are looking for.
-
Alertmanager SMTP configuration
You should take a look at "kube-prometheus-stack". It not only includes prometheus, node-exporter and Grafana but also a ton of preconfigured alerts and dashboards. Will save you a lot of work!
-
How do I find / edit Prometheus configuration after deploying it on Kubernetes ?
Since their are different ways to install what exactly did you install? Vanilla charts , stack, operator? https://github.com/prometheus-community/helm-charts/tree/main/charts
What are some alternatives?
cql-proxy - A client-side CQL proxy/sidecar.
tanka - Flexible, reusable and concise configuration for Kubernetes
postgres-operator - Postgres operator creates and manages PostgreSQL clusters running in Kubernetes
kube-thanos - Kubernetes specific configuration for deploying Thanos.
reaper-operator - Kubernetes operator for Cassandra Reaper
kube-prometheus - Use Prometheus to monitor Kubernetes and applications running on Kubernetes
cassandra-medusa - Apache Cassandra Backup and Restore Tool
kustomize - Customization of kubernetes YAML configurations
postgres-operator - Production PostgreSQL for Kubernetes, from high availability Postgres clusters to full-scale database-as-a-service.
pihole-kubernetes - PiHole on kubernetes
bank-vaults - A Vault swiss-army knife: A CLI tool to init, unseal and configure Vault (auth methods, secret engines).
pack - CLI for building apps using Cloud Native Buildpacks