Shulou(Shulou.com)06/01 Report--

What this article shares with you is about how to practice Network Policy. The editor thinks it is very practical, so I share it with you to learn. I hope you can get something after reading this article.

To demonstrate Network Policy, let's deploy a httpd application whose configuration file httpd.yaml is:

There are three copies of httpd and services are provided through Service of type NodePort. Deploy applications:

The cluster node can access the Service or Ping to the replica Pod.

Now create the following Network Policy:

Verify the validity of Network Policy:

Busybox Pod can no longer access Service.

The cluster node can no longer access the Service, and the Ping does not have access to the replica Pod.

If you want to make the application accessible to cluster nodes and outside the cluster (192.168.56.1), you can make the following modifications to Network Policy:

Now, the cluster nodes and outside the cluster (192.168.56.1) can be accessed:

In addition to restricting inbound traffic through ingress, you can also use egress to limit outbound traffic. You can refer to the relevant documents and examples on the official website, so I won't repeat them here.

Kubernetes uses a flat network model, and each Pod has its own IP and can communicate directly.

CNI specification allows Kubernetes to flexibly choose a variety of Plugin to implement cluster networks.

Network Policy endows Kubernetes with powerful network access control mechanism.

The above is how to practice Network Policy. The editor believes that there are some knowledge points that we may see or use in our daily work. I hope you can learn more from this article. For more details, please follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.