-
Notifications
You must be signed in to change notification settings - Fork 1.3k
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
Can't run linkerd top
in Windows Subsystem for Linux shell
#1976
Comments
@switchboardOp Thanks for reporting this! That's definitely unexpected. I'm unable to reproduce this with linkerd 2.1 on my test cluster. Can you confirm that you control plane is also running linkerd 2.1, but pasting the results of running |
And if you could also paste the logs from the
|
Looks like it can't connect to a particular IP (api server?), but I'm not sure what IP that is. It's not a pod or endpoint in the cluster.
|
Ah, that's (unfortunately) the expected log output. That process syncs with the kubernetes API, so 10.233.0.1:443 is the address of the kubernetes API server. When the process first starts, it attempts to sync, but the sync requests are routed through linkerd-proxy, and linkerd-proxy hasn't initialized yet. So it logs and retries, as expected. The sync eventually succeeds if you see the "caches synced" log message. To date, we haven't been able to suppress those messages due to kubernetes/kubernetes#61006, but that issue was resolved a month ago. I think that the next time we bump our k8s.io deps we could potentially fix the log output, but that's not the source of the Just to confirm, you don't see any additional logs after the "caches synced" message? You could retry reinstalling linkerd with the |
"caches synced" was the last line I got from the public-api container. Here's that same public-api log with debug on...
Nothing's jumping out at me, but then I am a linkerd newbie. |
Thanks for pasting the debug output. I agree -- that all looks sane to me. Out of curiosity, what system are you running the |
aha! I was running the command from my WSL shell running ubuntu 16.04 ssh'd into one of the masters (CentOS) and installed the cli. That seems to work. Thank you. Guess I'll avoid using |
@switchboardOp Glad we were able to get to the bottom of this! We can leave this issue open to track handling WSL better. At a minimum, if we can't draw the top table, we should display a more intelligible error message. Thanks for your help tracking this down. |
linkerd top
in Windows Subsystem for Linux shell
@switchboardOp what version of windows are you running?
my work laptop is running an older windows build, i can test tomorrow |
Looks like I am on an older build of Windows and the kernel @jon-walton.
I will try updating if it's not blocked by GPO 🤞 |
I just tested on an older build (1803) and it works:
I don't have any machines running anything older then 1803. I also tested with linkerd 2.1 stable which also works for me |
@switchboardOp Were you able to update to see if that fixes the issue with running |
I'm unable to update the Windows installation on my machine at this time. Definitely seems related to the older Windows build I'm running. |
I was able to install Windows 10 1709 and can confirm it doesn't work in WSL with this version of windows.
|
Looks like this was an issue specific to a unique windows version. Closing out for now. |
Bug Report
What is the issue?
Not able to run
linkerd top
as described in the getting-started guide.How can it be reproduced?
Follow the getting-started guide to deploy linkerd stable-2.1.0 on Kubernetes.
the command
linkerd -n linkerd top deploy/linkerd-web
from step 4 will fail.Logs, error output, etc
linkerd check
outputEnvironment
Possible solution
Additional context
I'm getting the same result on Kube 1.9.6 and 1.12.3
There's an issue with the external network for these cluster that's causing the linkerd-version check to fail, but I don't think that's the root cause here.
I've validated that the install is working otherwise by accessing the UI and running other
linkerd
commands.The text was updated successfully, but these errors were encountered: