-
Notifications
You must be signed in to change notification settings - Fork 79
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
Create Kubernetes logs input-plugin #154
Comments
Would it be possible to have a generic container plugin that can detect the runtime and automatically use/do the right thing under the hood without the person having to configure Logagent explicitly for Kubernetes or non-Kubernetes env? |
The start script can deal with different environments to configure LA. Well, the k8s user must mount /var/log into LA container to make the k8s plugin work. Therefore we will need Kubernetes specific installation instructions, and use k8s API instead of docker API. |
The following DaemonSet should work on IBM Cloud.
Note, we are still testing and have seen some crashes, which might be unrelated to the new Kubernetes input plugin. |
It turns out that Logagent restarts are caused by tail-forever on Node 10 mingqi/tailF#12 - sematext/logagent:2.0.146 ignores the uncaughtException until the issue gets fixed by a new release of tail-forever. We will try to create a pull-request or publish a new version of tail-forever node module. The final daemonset for a more stable deployment requires v2.0.146 or later:
|
Version sematext/loagagent:2.0.149 uses Node 8 and runs stable without exceptions. |
Problem with Node 10 was fixed mingqi/tailF#12 |
Logagent works fine with its docker-plugin on Kubernetes, when docker is used as container runtime. When containerd is used (e.g. IBM Cloud) the log collection via /var/run/docker.sock does not work.
I suggest creating a Kuberntes specific log collection plugin to avoid any trouble when alternative container runtimes are used in Kubernetes.
The text was updated successfully, but these errors were encountered: