We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
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
duplicate metrics
The destination controller logs:
failed to register Prometheus gauge Desc{fqName: \"job_cache_size\", help: \"Number of items in the client-go job cache\", constLabels: {cluster=\"local\"}, variableLabels: {}}: duplicate metrics collector registration attempted
with edge-24.6.1:
edge-24.6.1
linkerd install --crds | kubectl apply -f - linkerd install | kubectl apply -f - kubectl -n linkerd logs deploy/linkerd-destination -c destination
$ kubectl -n linkerd logs deploy/linkerd-destination -c destination time="2024-06-12T15:28:18Z" level=info msg="running version edge-24.6.1" time="2024-06-12T15:28:18Z" level=info msg="starting admin server on :9996" time="2024-06-12T15:28:18Z" level=info msg="Using default opaque ports: map[25:{} 587:{} 3306:{} 4444:{} 5432:{} 6379:{} 9300:{} 11211:{}]" time="2024-06-12T15:28:18Z" level=warning msg="failed to register Prometheus gauge Desc{fqName: \"job_cache_size\", help: \"Number of items in the client-go job cache\", constLabels: {cluster=\"local\"}, variableLabels: {}}: duplicate metrics collector registration attempted" time="2024-06-12T15:28:18Z" level=info msg="waiting for caches to sync"
linkerd check -o short
$ linkerd check -o short Status check results are √
$ kind version kind v0.22.0 go1.20.13 linux/amd64
No response
maybe
The text was updated successfully, but these errors were encountered:
No branches or pull requests
What is the issue?
The destination controller logs:
How can it be reproduced?
with
edge-24.6.1
:Logs, error output, etc
output of
linkerd check -o short
Environment
Possible solution
No response
Additional context
No response
Would you like to work on fixing this bug?
maybe
The text was updated successfully, but these errors were encountered: