Cilium.io Website Review

Get started with Cilium on KUBERNETES, DOCKER, MESOS, etc. in less than 15 minutes A microservices-based application is split into small independent services that communicate with each other via APIs using lightweight protocols like HTTP, GRPC, KAFKA and more. However, existing Linux network security mechanisms (e.g., iptables) only operate at the network and transport layers (i.e., IP addresses and ports) and lack visibility into the microservices layer. We believe in a future where Linux has de*p network visibility and control for microservice at the API layer, making applications more secure than ever before. If this goal excites you too, we invite you to join us by contributing ideas, code, and docu*entation to Cilium. Identity Based Security Cilium visibility and security policies are based on the container orchestrator identity (e.g., Kubernetes labels). Never again worry about network subnets or container IP addresses when writing security API-Protocol Visibility + Security Traditional firewalls only see and filter packets based on network headers like IP address and ports. Cilium can do this as well, but also understands and filters the individual HTTP, gRPC, and Kafka BPF is the underlying Linux superpower to do the heavy lifting on the datapath by providing sandboxed programmability of the Linux kernel Cilium was designed for scale, with no node-to-node interactions required when new pods are deployed, and all coordination through a