feat: add Jaeger tracing observability to OpenShift deployment #646
+155
−0
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Adds Jaeger all-in-one deployment for distributed tracing support in the semantic router dashboard. Fixes the "Jaeger not configured" error on the tracing page. Changes: - deploy/openshift/observability/jaeger/deployment.yaml: Jaeger all-in-one container with OTLP, gRPC, HTTP, and Zipkin endpoints - deploy/openshift/observability/jaeger/service.yaml: ClusterIP service exposing all Jaeger ports (UI:16686, OTLP:4317/4318, etc.) - deploy/openshift/observability/jaeger/route.yaml: OpenShift route for external Jaeger UI access Configuration: - Memory-based trace storage (10,000 max traces) - OTLP collector enabled for OpenTelemetry integration - No QUERY_BASE_PATH set to allow proper static asset loading through dashboard proxy - Security context with non-root user and dropped capabilities - Resource limits: 512Mi-1Gi memory, 250m-500m CPU The dashboard's existing Jaeger proxy configuration at router.go:317-350 handles proxying to http://jaeger:16686 via the TARGET_JAEGER_URL environment variable already configured in dashboard-deployment.yaml. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> Signed-off-by: Senan Zedan <[email protected]>
✅ Deploy Preview for vllm-semantic-router ready!
To edit notification comments on pull requests, go to your Netlify project configuration. |
Add Jaeger deployment to deploy-to-openshift.sh so all observability components (Grafana, Prometheus, Jaeger) can be deployed with a single command. The script includes conditional logic to gracefully handle cases where Jaeger deployment files may not exist. 🤖 Generated with [Claude Code](https://claude.com/claude-code) Co-Authored-By: Claude <[email protected]> Signed-off-by: Senan Zedan <[email protected]>
szedan-rh
force-pushed
the
fix_tracing
branch
from
95bb636 to
9256579
Compare
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Summary
Adds Jaeger all-in-one deployment for distributed tracing support. Fixes the "Jaeger not configured" error when accessing the tracing page at
/tracing.Changes
Configuration
Testing
Verified on OpenShift cluster: