<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:sy="http://purl.org/rss/1.0/modules/syndication/" xmlns:media="http://search.yahoo.com/mrss/"><channel><title>NodePort on Shaowen Chen's Website</title><link>https://www.chenshaowen.com/en/tags/nodeport/</link><description>Recent content in NodePort on Shaowen Chen's Website</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>&amp;copy;2016 - {year}, All Rights Reserved.</copyright><lastBuildDate>Wed, 23 Jun 2021 00:00:00 +0000</lastBuildDate><sy:updatePeriod>weekly</sy:updatePeriod><atom:link href="https://www.chenshaowen.com/en/tags/nodeport/atom.xml" rel="self" type="application/rss+xml"/><item><title>How to Configure NetworkPolicy for NodePort in Kubernetes</title><link>https://www.chenshaowen.com/en/blog/how-to-configure-networkpolicy-for-nodeport.html</link><pubDate>Wed, 23 Jun 2021 00:00:00 +0000</pubDate><atom:modified>Wed, 23 Jun 2021 00:00:00 +0000</atom:modified><guid>https://www.chenshaowen.com/en/blog/how-to-configure-networkpolicy-for-nodeport.html</guid><description>1. Background As shown above, the business team needs to isolate the services in a namespace, forbidding access from workloads in the bar namespace while allowing users to reach the service through a Load Balancer (LB) via NodePort. It is easy to write a network policy:
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 apiVersion: networking.</description><dc:creator>微信公众号</dc:creator><category>NetworkPolicy</category><category>Network</category><category>Kubernetes</category><category>Operations</category><category>Security</category><category>Learning</category><category>NodePort</category><category>Network Isolation</category></item></channel></rss>