Hello to everyone. 👋 I have a first, newbie, question about Kolide: is there a way to block/filter access at the "/login" page? I mean, I'd like to have the login page accessible only from internal (private) addresses, leaving the other connections opened to osquery agents from external as well. Is there any internal option to do it? Thanks!!

Hello there @cips! Here is how I did it for Security Onion using nginx - https://defensivedepth.com/2020/04/02/kolide-fleet-breaking-out-the-osquery-api-web-ui/

looks good @defensivedepth I need to revisit my kubernetes config to get fleet working with an ingress controller that supports gRPC so that I can apply ingress rules to the fleet ui. @Kyle did you have any luck in that regards?

Yes, but without TLS termination, I just used the LB cert on fleet (since everything else behind the LB is just HTTP/unencrypted) then passed through GRPCS traffic (not GRPC), to

/kolide.agent.Api

ok, thanks - I’ll probably revisit again soon. I’ve learnt a bit more about k8s since last week (that you need to restart ingress controllers after applying configmap changes apparently)