<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>DevOps &#8211; HU Xiaoxu</title>
	<atom:link href="https://blog.ihuxu.com/category/computer-science/devops/feed/" rel="self" type="application/rss+xml" />
	<link>https://blog.ihuxu.com</link>
	<description>a software engineer&#039;s blog</description>
	<lastBuildDate>Wed, 03 Sep 2025 14:32:12 +0000</lastBuildDate>
	<language>en-US</language>
	<sy:updatePeriod>
	hourly	</sy:updatePeriod>
	<sy:updateFrequency>
	1	</sy:updateFrequency>
	<generator>https://wordpress.org/?v=6.6.2</generator>
	<item>
		<title>How to Expose the Kubernetes Service via  NodePort</title>
		<link>https://blog.ihuxu.com/how-to-expose-the-kubernetes-service-via-nodeport/</link>
					<comments>https://blog.ihuxu.com/how-to-expose-the-kubernetes-service-via-nodeport/#respond</comments>
		
		<dc:creator><![CDATA[HU Xiaoxu]]></dc:creator>
		<pubDate>Wed, 03 Sep 2025 14:25:52 +0000</pubDate>
				<category><![CDATA[Computer Science]]></category>
		<category><![CDATA[DevOps]]></category>
		<category><![CDATA[K8s]]></category>
		<category><![CDATA[NodePort]]></category>
		<guid isPermaLink="false">https://blog.ihuxu.com/?p=12669</guid>

					<description><![CDATA[In the previous article, we discussed the ClusterIP service type. In this one, we&#8217;ll briefly cover the NodePort service type, which allows us to expose a service as an entry point to the public network. Kubernetes Manifests Example As we can see from the above K8s manifests You can run the following commands to try this out locally using kind. Firstly, we need to configure the cluster to map your<div class="read-more"><a class="btn read-more-btn" href="https://blog.ihuxu.com/how-to-expose-the-kubernetes-service-via-nodeport/">Read More</a></div>]]></description>
		
					<wfw:commentRss>https://blog.ihuxu.com/how-to-expose-the-kubernetes-service-via-nodeport/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
		<item>
		<title>How the Kubernetes ClusterIP Service Works</title>
		<link>https://blog.ihuxu.com/how-the-kubernetes-clusterip-service-works/</link>
					<comments>https://blog.ihuxu.com/how-the-kubernetes-clusterip-service-works/#respond</comments>
		
		<dc:creator><![CDATA[HU Xiaoxu]]></dc:creator>
		<pubDate>Mon, 01 Sep 2025 16:11:01 +0000</pubDate>
				<category><![CDATA[Computer Science]]></category>
		<category><![CDATA[DevOps]]></category>
		<category><![CDATA[ClusterIP]]></category>
		<category><![CDATA[K8s]]></category>
		<guid isPermaLink="false">https://blog.ihuxu.com/?p=12665</guid>

					<description><![CDATA[A ClusterIP Service is the default Kubernetes service type. It provides a virtual IP address (VIP) inside the cluster to allow pods to communicate with each other. It is internal-only, meaning it is not accessible from outside the cluster. Example Manifests You can try it out by running the following commands Apply the Kubernetes manifest to the test cluster kind-my-cluster. If the test cluster doesn’t exist, you can create it<div class="read-more"><a class="btn read-more-btn" href="https://blog.ihuxu.com/how-the-kubernetes-clusterip-service-works/">Read More</a></div>]]></description>
		
					<wfw:commentRss>https://blog.ihuxu.com/how-the-kubernetes-clusterip-service-works/feed/</wfw:commentRss>
			<slash:comments>0</slash:comments>
		
		
			</item>
	</channel>
</rss>
