-
Notifications
You must be signed in to change notification settings - Fork 2.5k
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
[Bug]: HotRod example fails documented kustomize build #4230
Labels
Comments
Changing the kustomization to |
cc @highb |
@bigfleet I'll add this to my backlog or, if you want to open a PR to fix it, I can review. |
@highb ready to review |
yurishkuro
pushed a commit
that referenced
this issue
Feb 13, 2023
Signed-off-by: Jim Van Fleet <jim@jimvanfleet.com> ## Which problem is this PR solving? - Resolves #4230 ## Short description of the changes - Updating the document to include the updated all-in-one path - Adding one additional comment for those not briefed on kustomize Signed-off-by: Jim Van Fleet <jim@jimvanfleet.com>
Thanks for reviewing it @yurishkuro ! It's been a busy week for me. 😮💨 |
shubbham1215
pushed a commit
to shubbham1215/jaeger
that referenced
this issue
Feb 22, 2023
Signed-off-by: Jim Van Fleet <jim@jimvanfleet.com> ## Which problem is this PR solving? - Resolves jaegertracing#4230 ## Short description of the changes - Updating the document to include the updated all-in-one path - Adding one additional comment for those not briefed on kustomize Signed-off-by: Jim Van Fleet <jim@jimvanfleet.com>
shubbham1215
pushed a commit
to shubbham1215/jaeger
that referenced
this issue
Mar 5, 2023
Signed-off-by: Jim Van Fleet <jim@jimvanfleet.com> ## Which problem is this PR solving? - Resolves jaegertracing#4230 ## Short description of the changes - Updating the document to include the updated all-in-one path - Adding one additional comment for those not briefed on kustomize Signed-off-by: Jim Van Fleet <jim@jimvanfleet.com> Signed-off-by: shubbham1215 <sawaikershubham@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
What happened?
As a Jaeger newbie
I want to see how to run an example app on Kubernetes
So that I can see how traffic flows from an application to sidecar to jaeger collector with or without OpenTelemetry
Steps to reproduce
main
branchexamples/hotrod
kustomize build ./kubernetes | kubectl apply -f -
Expected behavior
I expected
kustomize build
to create YAML resources and forkubectl apply
to apply them.Relevant log output
Screenshot
No response
Additional context
It does appear that the kustomization once targeted a
jaeger
directory, and now there is ajaeger-all-in-one
-- that change tokustomization.yaml
is not enough, though:I would help, but I am trying to learn myself! I appreciate there's a lot of attention on docker, but hopefully there are some cycles for learning on the cluster.
Jaeger backend version
v1.42
SDK
Whatever hotrod is using, hopefully.
Pipeline
I would like to ultimately monitor what the sidecar injection does without any other influence to determine if that's possible for my use case.
Stogage backend
Memory
Operating system
n/a
Deployment model
Kuberntes
Deployment configs
All contained in the repo
The text was updated successfully, but these errors were encountered: