<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Infrastructure on DefinIT</title><link>https://www.definit.co.uk/category/infrastructure/</link><description>Recent content in Infrastructure on DefinIT</description><generator>Hugo -- gohugo.io</generator><language>en</language><copyright>© 2026</copyright><lastBuildDate>Fri, 15 May 2026 00:00:00 +0000</lastBuildDate><atom:link href="https://www.definit.co.uk/category/infrastructure/index.xml" rel="self" type="application/rss+xml"/><item><title>Running HashiCorp MCP Servers as a Shared Kubernetes Service</title><link>https://www.definit.co.uk/2026/05/running-hashicorp-mcp-servers-as-a-shared-kubernetes-service/</link><pubDate>Fri, 15 May 2026 00:00:00 +0000</pubDate><guid>https://www.definit.co.uk/2026/05/running-hashicorp-mcp-servers-as-a-shared-kubernetes-service/</guid><description>&lt;p&gt;If you&amp;rsquo;ve been following along with my posts on configuring AI tooling for infrastructure work, most of the examples have involved running an MCP server locally. Running a process on your machine with credentials in your environment on a port that only you can reach gets you up and running quickly, which is great for getting started, but has limitations.&lt;/p&gt;</description><media:content xmlns:media="http://search.yahoo.com/mrss/" url="https://www.definit.co.uk/2026/05/running-hashicorp-mcp-servers-as-a-shared-kubernetes-service/featured.png"/></item></channel></rss>