-
Notifications
You must be signed in to change notification settings - Fork 622
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
does this tool work outside Google? #21
Comments
@sols1 It should work. I started a random pod, and then exec into the pod:
Which K8s version are you using? |
When I try to do the same thing on my k8s cluster I get different result:
As you can see many pods are running but /var/run/secrets/kubernetes.io/serviceaccount/token does not exist. |
I'll make sure whether the token file is set by default. At least according to the document, for pod in |
As you can see from above I am running several pods in kube-system namespace and those don't have this token file either:
|
kubernetes version ~1.3 |
The thing that might be unusual about this setup is that kubernetes runs on top of RancherOS, which is containerized. But when I am trying to access this file inside host namespace I get the same result:
Or inside kubelet container:
Or kube-proxy:
|
I believe you need to enable the
That may be the reason, it looks like |
Yes, serviceaccount does not show any secrets:
And yes, there is no --admission-control option in apiserver. But nothing says it is a required option, particularly for bare metal cluster. This brings back the original question: is this tool supposed to work for any k8s cluster? |
@sols1 It is supposed to be. If there is no admission control, and the pod could talk with apiserver without auth, then it should still work. I'll see whether we could fix it. |
@sols1 Please see kubernetes/kubernetes#27973 (comment). :) |
Even after this #kubernetes/kubernetes#27973 (comment) I got:
So, which version of OS is supported? Also, is there another option necessary to change |
@sols1 This is because node-problem-detector uses The apiserver before kubernetes/kubernetes#26381 didn't allow patch operation on node status. I believe that your kubernetes version doesn't contain kubernetes/kubernetes#26381 yet. |
@sols1 And from the log, it seems that the kernel log is not at |
@Random-Liu Hi. I'm facing the same issue. The thing is, I have been running my cluster without I was facing a similar situation when trying to run heapser, but it has an option |
@ApsOps That's quite useful. I'll also add a |
@Random-Liu Maybe we can refer to Heapster for it's convenience to deploy both in Kubernetes cluster and stand alone. |
We may close this once #49 is merged. @sols1 @ApsOps @Random-Liu |
Close this one since #49 is merged. Please take look at the document about how to use the newly introduced |
@Random-Liu I'm unable to build (I've seen the open issue regarding journald usage). I also tried using image that @shyamjvs pushed (tagged v0.3), but it fails with
It seems to be missing a few commits or I might be doing something wrong in config. Could you please release a docker image, or suggest something I can try? :) |
@ApsOps To build, you need to install libsystemd-journal-dev or libsystemd-dev to build it for journald support for the journald support.
The error seems to me that you set I've tried v0.3 myself and it seems to work for me except a recently introduced issue #61.
The issue is tracked here #60. |
Ah, makes sense. I had |
OK. Then the README is a bit misleading then. Could you file an issue or pr for this? Thanks a lot~ :) @ApsOps |
Panic crash:
The text was updated successfully, but these errors were encountered: