strimzi-kafka-operator
poc-files
strimzi-kafka-operator | poc-files | |
---|---|---|
6 | 1 | |
4,468 | 0 | |
1.6% | - | |
9.8 | 7.1 | |
2 days ago | 4 months ago | |
Java | Python | |
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.
strimzi-kafka-operator
-
Knative switchboard series, part 1. Setup Knative Eventing with Kafka from scratch, scale based on events volume, and monitor
Knative dashboards together with Kafka's dashboards it sheds light on almost any aspect of what's going on in the system.
- How to self host Apache Kafka?
-
Am I wrong for avoiding helm completely?
Strimzi is an operator for deploying Kafka in K8s, and makes extensive use of CRs. E.g., https://github.com/strimzi/strimzi-kafka-operator/blob/0.31.1/examples/kafka/kafka-persistent.yaml
-
Prometheus Additional Scrape Config node metrics limitation
But I encountered a problem. In the example files they provide prometheus-additional.yaml file which is referred to in prometheus.yaml as additionalScrapeConfigs field. It collects Kubernetes node metrics for which it has panels in example Grafana dashboards. All good. But the problem is, the prometheus-additional.yaml file has a field called namespaces: names: [] (File can be seen here - https://github.com/strimzi/strimzi-kafka-operator/blob/main/examples/metrics/prometheus-additional-properties/prometheus-additional.yaml) in kubernetes_sd_configs.
- How to renew Certificate in Strimzi Kafka entity operator.
- Kafka cluster and its maintenance, what is it like?
poc-files
-
Knative switchboard series, part 1. Setup Knative Eventing with Kafka from scratch, scale based on events volume, and monitor
Follow Strimzi quickstart to install kafka in knative-eventing namespace, but use different Kafka cluster definition, see below. Knative workloads are expecting to be run in knative-eventing namespace, otherwise issues arise. And it's easier to keep Knative and Kafka in one namespace. Use kafka-cluster.yaml as kafka cluster resource instead of the one used in Strimzi quickstart (kafka-single-persistent.yaml). If you're not limited on disk, best to set storage: size: 50Gi or 100Gb in kafka-cluster yaml, and at least 25Gb for zookeeper storage. For trial quota, you're limited to 20Gb and 10Gb for zookeeper (if we're doing 2 Kafka clusters, if one - can be more).
What are some alternatives?
kattlo-cli - Kattlo CLI Project
container-jfr - Secure JDK Flight Recorder management for containerized JVMs
langstream - LangStream. Event-Driven Developer Platform for Building and Running LLM AI Apps. Powered by Kubernetes and Kafka.
workflow - The developer and operations friendly Kubernetes toolbox
hephy-workflow-beta - Beta chart for Hephy Workflow (test only)
flux2-kustomize-helm-example - A GitOps workflow example for multi-env deployments with Flux, Kustomize and Helm.
RemoteCodeCompiler - An online code compiler supporting 11 programming languages (Java, Kotlin, Scala, C, C++, C#, Golang, Python, Ruby, Rust and Haskell) for competitive programming and coding interviews.
gcs-connector-for-apache-kafka - Aiven's GCS Sink Connector for Apache Kafka®
ns4kafka - Ns4Kafka brings namespaces on top of Kafka brokers, Kafka Connect and Schema Registry.
grafana-dashboard-from-metric-list - Create grafana dashboard from metric list and uid of datasource
kafka-ui - Open-Source Web UI for Apache Kafka Management
covid19-vaccine-tracker - Covid19 Vaccine Tracker and Telegram Bot for India