<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Nsx on Will Arroyo</title><link>https://blog.warroyo.com/tags/nsx/</link><description>Recent content in Nsx on Will Arroyo</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026 Will Arroyo</copyright><lastBuildDate>Thu, 21 Sep 2023 17:50:32 +0000</lastBuildDate><atom:link href="https://blog.warroyo.com/tags/nsx/index.xml" rel="self" type="application/rss+xml"/><item><title>Setting static IPs for workloads in TKG</title><link>https://blog.warroyo.com/posts/setting-static-ips-for-workloads-in-tkg/</link><pubDate>Thu, 21 Sep 2023 17:50:32 +0000</pubDate><guid>https://blog.warroyo.com/posts/setting-static-ips-for-workloads-in-tkg/</guid><description>&lt;p&gt;A question comes up often of how can a static IP be set for workloads running in TKG. The answer is generally &amp;ldquo;It depends&amp;rdquo; and then followed by a series of questions about why it&amp;rsquo;s needed and if there are alternatives that could be done etc. In many scenarios, this is needed so that workloads running in a container on TKG can be identified by an external firewall and be allowed to talk to some external service. For example, maybe a workload needs to get access to a particular database and it has a strict access policy based on IP.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://blog.warroyo.com/posts/setting-static-ips-for-workloads-in-tkg/featured.png"/></item></channel></rss>