Re:Show HN: LogDNA – Set up Kubernetes logging with 2 kubect...
by leeab on Wednesday March 15, 2017 @02:15PM
(#13878403)
Ahh yes, thanks for catching that. I just made a note that we collect from all namespaces currently.
Yeah, we now set our agent up w/o namespaces. During our beta, we originally had it set up inside `kube-system` but 2 of our testers mentioned that the pod wouldn't install unless it was in `default`. So we moved it out of `kube-system` but we still weren't sure what caused the issue since it worked fine on our cluster. We were using Kubernetes v1.4 so it could've been an older version issue.
Re:Show HN: LogDNA – Set up Kubernetes logging with 2 kubect...
by lobster_johnson on Wednesday March 15, 2017 @02:45PM
(#13878643)
Actually, kube-system is the right namespace for things like this.
I don't know why it didn't work -- maybe they put the secret in the wrong namespace?
Re:Show HN: LogDNA – Set up Kubernetes logging with 2 kubect...
by leeab on Wednesday March 15, 2017 @02:52PM
(#13878698)
Yeah one of those mysteries of life. :/ One day we'll probably go back and try this on a few older versions to see if we can repro what happened. But yeah, it was right off the bat when we started our beta, 2 different people said they had to modify the yaml in order to get it to work (something we wanted to avoid altogether).
As I have understood,you do not set any namespace for the secret/daemonset, which is fine with me.
But this way, I could install multiple agents (for each namespace).
So a better documentation about the best practice installation for multiple namespaces would be nice.