Skip to content
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

Weave Scope does not record the pod topology when there is only job(not cronjob) in kubernetes #3864

Open
shabicheng opened this issue May 30, 2021 · 1 comment · May be fixed by #3865
Open

Comments

@shabicheng
Copy link

What you expected to happen?

When there is only a job in my kubernetes cluster, Weave Scope does not show the topology of the pod created by this job.

I have debugged the code and found that Scope only calculates the topology when cronJob exists. And looks like when there are more than one cronJob, job selector will register many times.

https://github.com/weaveworks/scope/blob/master/probe/kubernetes/reporter.go#L664

What happened?

How to reproduce it?

Anything else we need to know?

Versions:

$ scope version
$ docker version
$ uname -a
$ kubectl version

Logs:

$ docker logs weavescope

or, if using Kubernetes:

$ kubectl logs <weave-scope-pod> -n <namespace> 
shabicheng added a commit to aliyun-sls/scope that referenced this issue May 30, 2021
@shabicheng
Copy link
Author

I think this is a bug, and I have fixed this and will create a PR for it. thanks a lot~

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant