proxmox

Deploy CrowdSec to Protect Your Services From Bad Actors & Common

Deploy CrowdSec to Protect Your Services From Bad Actors & Common Attacks – Kubernetes

#Deploy #CrowdSec #Protect #Services #Bad #Actors #Common

“Jim’s Garage”

Deploy CrowdSec in Kubernetes to protect your apps from hackers. Use live threat data to ban bad IPs and threat actors, protect your services from compromise, and have real-time alerting.

Video Files:

@crowdsec…

source

 

To see the full content, share this page by clicking one of the buttons below

Related Articles

6 Comments

  1. Hello Jim, I use Cilium CNI for my RKE2 and the Local TrafficPolicy works well. Also I really recommend Cilium as it has a built in LB feature (you can ditch metalLB then), has also network policy, eBPF and much more

  2. I just checked the docs of RKE2. But there really, doesn't seem to be any mention or feature flag for the local traffic policy.

    I think you have to options to get it working: The first would be to use the ProxyProtocol, which would require you to run a LoadBalancer like HAProxy (instead of metalllb/kube-vip) in front of traefik. The second option would be to use Cilium and use it to replace kube-proxy. You might need to use DSR as well and/or k8s v1.28+ as they removed some iptables code from kubelet in that release. No idea why it was even in there…

  3. Hi, I have several networks. They are all for nat and I don't have a dedicated address. If I buy the cheapest vds, what should I put there and how to set up switching and routing?My clients will be either microtic or keenetic. How would you act in such a situation?

Leave a Reply