Hacker Newsnew | past | comments | ask | show | jobs | submitlogin

> It's the worst, I don't even get to see my server logs because "that would mean giving you access to the entire thing". I'm not a k8s person but surely that has to be missing something.

I'm pretty sure it's possible to configure access to logs, not to the entire thing (whatever that means). He's probably lazy and does not want to bother.

Besides, you should have centralized logging using loki or something similar. Kubernetes logging is not enough for any reasonable use-case.



I know, but we don't get any. I legit had to do logging on my end to a _database_ because they weren't a fan of something like say new relic or similar.


Isn't that just because Kubernetes makes it unreasonably hard to configure access to logs like that?


It's really not that hard if you got proper users.

But doing proper users on k8s is hard. I suspect they just run with admin credentials and no real way to generate users.


For small cluster you can just create service account for a user, create token for it and write it in the kubeconfig. Then assign role to this service account and that's about it.

The main issue with this approach is that you can't organize those "users" into a groups. But for a small number of users you can just create all rolebindings and be done with it.


Yes. I was thinking of that for a moment as well. But it requires some understanding and is annoying in various ways.

I should look into how to provision users at some point. but OTOH GKE takes care of it for our prod, and other clusters can be run with just admin.


No, it is simple to setup.




Guidelines | FAQ | Lists | API | Security | Legal | Apply to YC | Contact

Search: