-
Notifications
You must be signed in to change notification settings - Fork 55
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
Oracle Cloud Infrastructure's Kubernetes support #108
Comments
I am running also into the problem that the setup with logDNA works out of the box, but I cannot see any logging output other then "kubernetes administration" output. An excerpts:
However, I tried the v2 DeamonSet and that seems to work in the beginning, I can see some outputs from my pods, but then it prints out the following warning in each pod of logdna-agent:
And there is no output thereafter from my pods again. There is still administration output like the one mentioned above. |
Yes, so adding actually your change to the |
21 08:16:15 LogDNASample LogDNA Sample App INFO type=CRYPTO_KEY_USER msg=audit(1539953067.158:1156938): pid=14611 uid=0 auid=4294967295 ses=4294967295 subj=system_u:system_r:sshd_t:s0-s0:c0.c1023 msg='op=destroy kind=session fp=? direction=both spid=14612 suid=74 rport=40868 laddr=10.11.5.50 lport=22 exe="/usr/sbin/sshd" hostname=? addr=109.104.88.43 terminal=? res=success' |
OCI Container Engine for Kubernetes (OKE) outputs logs to the user data mount point in /u01. The fix is to just mount /u01 to give the agent access to the logs. See #107 for the fix
The text was updated successfully, but these errors were encountered: