-
Notifications
You must be signed in to change notification settings - Fork 26
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
NETOBSERV-256: Kafka config #107
Changes from 3 commits
6a2229f
27d24cd
9d18741
8887cc4
1f71fe1
File filter
Filter by extension
Conversations
Jump to
Diff view
Diff view
There are no files selected for viewing
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -22,6 +22,21 @@ undeploy-loki: ## Undeploy loki. | |
curl -S -L https://raw.githubusercontent.com/netobserv/documents/main/examples/zero-click-loki/1-storage.yaml | kubectl --ignore-not-found=true delete -f - || true | ||
-pkill --oldest --full "3100:3100" | ||
|
||
.PHONY: deploy-kafka | ||
deploy-kafka: | ||
@echo -e "\n==> Deploy kafka" | ||
kubectl create namespace $(NAMESPACE) --dry-run=client -o yaml | kubectl apply -f - | ||
kubectl create -f "https://strimzi.io/install/latest?namespace="$(NAMESPACE) -n $(NAMESPACE) | ||
kubectl create -f "https://raw.githubusercontent.com/netobserv/documents/main/examples/kafka-cluster.yaml" -n $(NAMESPACE) | ||
kubectl create -f "https://raw.githubusercontent.com/netobserv/documents/main/examples/kafka-topic.yaml" -n $(NAMESPACE) | ||
|
||
.PHONY: undeploy-kafka | ||
undeploy-kafka: ## Undeploy loki. | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. change comment from There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done, thanks! |
||
@echo -e "\n==> Undeploy kafka" | ||
kubectl delete -f "https://raw.githubusercontent.com/netobserv/documents/main/examples/kafka-topic.yaml" -n $(NAMESPACE) | ||
kubectl delete -f "https://raw.githubusercontent.com/netobserv/documents/main/examples/kafka-cluster.yaml" -n $(NAMESPACE) | ||
kubectl delete -f "https://strimzi.io/install/latest?namespace="$(NAMESPACE) -n $(NAMESPACE) | ||
|
||
.PHONY: deploy-grafana | ||
deploy-grafana: ## Deploy grafana. | ||
@echo -e "\n==> Deploy grafana" | ||
|
@@ -48,4 +63,3 @@ deploy-all: manifests generate fmt lint deploy-loki deploy-grafana install deplo | |
|
||
.PHONY: undeploy-all | ||
undeploy-all: undeploy-loki undeploy-grafana uninstall undeploy-sample-cr | ||
|
Original file line number | Diff line number | Diff line change |
---|---|---|
|
@@ -30,6 +30,10 @@ spec: | |
enableKubeProbes: true | ||
healthPort: 8080 | ||
prometheusPort: 9090 | ||
kafka: | ||
enable: false | ||
address: "kafka-cluster-kafka-bootstrap" | ||
topic: "flp-topic" | ||
There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. as this CR will define the default values in OLM, I'd use a topic name that better describes what it is for. Maybe "netflows" ? There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Actually, There was a problem hiding this comment. Choose a reason for hiding this commentThe reason will be displayed to describe this comment to others. Learn more. Done, thanks! |
||
loki: | ||
url: 'http://loki:3100/' | ||
batchWait: 1s | ||
|
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Since we mix both
strimzi.io
/netobserv/document
sources, we should fix the version here instead of using latestThere was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Strimzi only provide this endpoint for its latest version.
The other option is to track this file in one of our repository, but this file has to be changed depending of the targeted namespace.
Since we only use this for now as quick setup for development and since this file is quite big (13k lines) would you be fine to keep using latest for know? If at one point we experience issues it will still be possible to freeze the version there.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Well if there is no easy solution let's keep this as is. Thanks