Network Policies Provide Control and Security for Kubernetes Applications

4th chunk of `content/en/blog/_posts/2016-04-00-Kubernetes-Network-Policy-APIs.md`

e0b9e0d921042fefa855db5f9058cb306a8b3df548e5fdaf00000001000003fc

![controller.jpg](https://lh5.googleusercontent.com/zMEpLMYmask-B-rYWnbMyGb0M7YusPQFPS6EfpNOSLbkf-cM49V7rTDBpA6k9-Zdh2soMul39rz9rHFJfL-jnEn_mHbpg0E1WlM-wjU-qvQu9KDTQqQ9uBmdaeWynDDNhcT3UjX5)





If you’ve been holding back on developing applications with Kubernetes because of network isolation and/or security concerns, these new network policies go a long way to providing the control you need. No need to wait until Kubernetes 1.3 since network policy is available now as an experimental API enabled as a ThirdPartyResource.



If you’re interested in Kubernetes and networking, there are several ways to participate - join us at:

- Our [Networking slack channel](https://kubernetes.slack.com/messages/sig-network/)&nbsp;
- Our [Kubernetes Networking Special Interest Group](https://groups.google.com/forum/#!forum/kubernetes-sig-network) email list&nbsp;


The Networking “Special Interest Group,” which meets bi-weekly at 3pm (15h00) Pacific Time at [SIG-Networking hangout](https://zoom.us/j/5806599998).

Title: Network Policies Provide Control and Security for Kubernetes Applications

Summary

The new network policies in Kubernetes address network isolation and security concerns, enabling application development. Network policy is available now as an experimental API enabled as a ThirdPartyResource, so you don't need to wait for Kubernetes 1.3 to take advantage of the feature. The Kubernetes Networking Special Interest Group (SIG) offers various channels for participation, including a Slack channel, email list, and bi-weekly meetings.