Apply the same rules everywhere — traditional networks and Kubernetes alike
The problem
- Keeping departments, customers, or environments cleanly separated usually means separate tools for traditional network segmentation and for Kubernetes.
The solution
- Tobogganing applies the same routing and segmentation controls to conventional infrastructure and to Kubernetes pods, from the same platform.
Outcomes
- One security model to maintain, not one per environment.
- New environments — including Kubernetes clusters — plug into rules that already exist instead of starting from scratch.