-
Notifications
You must be signed in to change notification settings - Fork 77
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
fix make k8s/metrics/jaeger/deploy failure #2077
Conversation
[CHATOPS:HELP] ChatOps commands.
|
I think it would be better to use curl and send an Empty Body and wait for a 400 Badrequest to be returned. |
Deploying with Cloudflare Pages
|
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.
LGTM!!
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.
LGTM!
/rebase |
[REBASE] Rebase triggered by kmrmt for branch: bugfix/makefile/k8s-jaeger-deployment-failure |
[REBASE] Failed to rebase. |
67d5660
to
db0e0fc
Compare
Description:
When running
make k8s/metrics/jaeger/deploy
, in my environment, executingkubectl apply -f k8s/metrics/jaeger/jaeger.yaml
fails with errors below.I watched logs, but I could not find the related error.
So it is my opinion, even if it checks the condition using
kubectl wait --for=condition=ready pod -l app.kubernetes.io/name=jaeger-operator --timeout=60s
, the endpoint will not be ready depending on the performance of the computer.Finally, in my environment, it could deploy in less than 3 seconds in most situation. And, to be sure, I estimated the buffer to be 5 seconds.
Related Issue:
Versions:
Checklist:
Special notes for your reviewer: