-
Notifications
You must be signed in to change notification settings - Fork 156
The Deployment "jaeger" is invalid #120
Comments
@boyoyon8 would you be open to sending your recommended change as a PR? |
I am experiencing this issue too. Any updates @fredrikssongustav ? |
@fredrikssongustav, if you are stuck, let us know and we can try to help! |
@jpkrohling I got kinda stuck on it. Or well, I was able to run the build successfully in minikube by running the commands in bash that travisci goes through here https://travis-ci.org/jaegertracing/jaeger-kubernetes/jobs/625339244?utm_medium=notification&utm_source=github_status and concluded something was fishy about travis. And frankly, I was able to apply the necessary configurations from my fork so I was able to debug my jaeger setup locally and kinda forgot about this 😅 But I'd love to close it if you have any ideas? |
That specific job is failing due to formatting problems:
This one can be fixed with |
Would love to get this resolved as it breaks our Opentracing example for most users: https://github.com/nginxinc/kubernetes-ingress/tree/master/examples/opentracing#step-2---deploy-a-tracer Happy to try opening a PR sometime next week if not resolved. - I'm not very knowledgable about TravisCI either though. 😄 |
No need to be a Travis expert: with a local |
@jpkrohling On my minikube when running
¯\_(ツ)_/¯ |
I got the same when running it locally. Travis logs: |
I got a different one when running locally:
@pavolloffay: have you seen this before? Looks like the Arquillian tests are failing both on master and for this PR. |
@pavolloffay ping. 😬 Sounds like the |
Were you able to run the test locally? |
Running [ERROR] Failed to execute goal org.apache.maven.plugins:
maven-failsafe-plugin:2.20.1:
integration-test (run-integration-tests) on project jaegertracing-kubernetes-all-in-one:
Execution run-integration-tests of goal org.apache.maven.plugins:maven-failsafe-plugin:2.20.1:integration-test failed.:
NullPointerException -> [Help 1] Currently testing against master. I'm not sure if that is helpful. Or if that's what you meant. |
@pavolloffay any update on this? |
Requirement - what kind of business use case are you trying to solve?
in
Problem - what in Jaeger blocks you from solving the requirement?
appear this message & jaeger-query not access on browser
Proposal - what do you suggest to solve the problem or improve the existing situation?
Change the yml according to kubernates 1.16 api
changed yml
The text was updated successfully, but these errors were encountered: