Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Kafka-Minion as alternative to Burrow for consumer lag monitoring #259

Merged
merged 17 commits into from
May 6, 2019
Merged
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Next Next commit
A heavy kustomization like this one is clearly only an example
  • Loading branch information
solsson committed May 6, 2019
commit 7fcabf3f636149570e4abc6a1b4cb134dacfb218
4 changes: 0 additions & 4 deletions variants/prometheus-operator-baseexample/kustomization.yaml

This file was deleted.

Original file line number Diff line number Diff line change
@@ -1,12 +1,10 @@
bases:
# With prometheus-operator only you must add your own Prometheus and Alertmanager resources
#- github.com/coreos/prometheus-operator?ref=de9a6e1
- github.com/coreos/kube-prometheus?ref=3a64636
- ../../consumers-prometheus
# The ../../prometheus base must be edited to point to the chosen kafka base
#- ../../prometheus
- ../../consumers-prometheus
# Resources won't apply without a prior apply -k with for example one of:
#- github.com/coreos/prometheus-operator?ref=de9a6e1
#- ../prometheus-operator-baseexample
# TEMP:
- ../../../unhelm/kube-prometheus
resources:
- k8s-kafka-rbac.yaml
# with base ../../prometheus