Kubernetes Network Policy Recipes Logo

Kubernetes Network Policy Recipes

0
Free
Visit Website

This repository contains various use cases of Kubernetes Network Policies and sample YAML files to leverage in your setup. If you ever wondered how to drop/restrict traffic to applications running on Kubernetes, read on. Easiest way to try out Network Policies is to create a new Google Kubernetes Engine cluster. Applying Network Policies on your existing cluster can disrupt the networking. At the time of writing, most cloud providers do not provide built-in network policy support. If you are not familiar with Network Policies at all, I recommend reading my Securing Kubernetes Cluster Networking article first. NetworkPolicies operate at layer 3 or 4 of OSI model (IP and port level). They are used to control the traffic in(ingress) and out(egress) of pods. An empty selector will match everything. For example spec.podSelector: {} will apply the policy to all pods in the current namespace. Selectors can only select Pods that are in the same namespace as the NetworkPolicies. Eg. spec.podSelector of an ingress rule can only select pods in the same namespace.

FEATURES

ALTERNATIVES

A lookup service for AS-numbers and prefixes by country

A simple text viewer for Prompt(1) sessions

A simple command-line tool that scans a website for CORS misconfigurations

A utility to generate malicious network traffic for security evaluation.

AWS Network Firewall provides fine-grained control over network traffic and enables easy deployment of firewall security.

A tool for discovering open S3 Buckets starting from a domain using various techniques such as crawling and DNS crawling.

A Linux command-line tool that allows you to kill in-progress TCP connections based on a filter expression, useful for libnids-based applications that require a full TCP 3-way handshake for TCB creation.

Smart traffic sniffing tool for penetration testers