-
Notifications
You must be signed in to change notification settings - Fork 13
fix: Make bufstream hostname configurable for weave-trace #559
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
base: main
Are you sure you want to change the base?
Conversation
The weave-trace-configmap had a hardcoded KAFKA_BROKER_HOST value of "bufstream.bufstream.svc.cluster.local", which prevented customers from deploying bufstream in custom namespaces. When customers used bufstream.namespaceOverride (e.g., wandb-bufstream), weave-trace and weave-trace-worker could not connect to the correct bufstream service. - Updated wandb.kafka.brokerHost helper in _queues.tpl to return full FQDN including namespace when bufstream is installed - Changed weave-trace.yaml to use the helper function instead of hardcoded value - Added fallback to "bufstream.bufstream.svc.cluster.local" when neither kafka nor bufstream are installed locally (assumes external bufstream)
📝 WalkthroughWalkthroughUpdated Helm chart templates to make Kafka broker host/port resolution dynamic and namespace-aware: bufstream host resolution now uses release namespace with override support, weave-trace uses template lookups for broker host and port, and chart version was bumped. Changes
Estimated code review effort🎯 3 (Moderate) | ⏱️ ~20 minutes Possibly related PRs
Suggested reviewers
Poem
🚥 Pre-merge checks | ✅ 3✅ Passed checks (3 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
dacbd
left a comment
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.
Something funky is going on; the snapshots' namespace shouldn't be changing.
The weave-trace-configmap had a hardcoded KAFKA_BROKER_HOST value of "bufstream.bufstream.svc.cluster.local", which prevented customers from deploying bufstream in custom namespaces. When customers used bufstream.namespaceOverride (e.g., wandb-bufstream), weave-trace and weave-trace-worker could not connect to the correct bufstream service.
Summary by CodeRabbit
Refactor
Chore