<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Kubernetes on Bryan Avery</title><link>https://bryanavery.co.uk/categories/kubernetes/</link><description>Recent content in Kubernetes on Bryan Avery</description><generator>Hugo -- gohugo.io</generator><language>en-GB</language><copyright>© 2026 Bryan Avery.</copyright><lastBuildDate>Mon, 27 Jan 2020 13:20:10 +0000</lastBuildDate><atom:link href="https://bryanavery.co.uk/categories/kubernetes/index.xml" rel="self" type="application/rss+xml"/><item><title>Kubernetes</title><link>https://bryanavery.co.uk/kubernetes/</link><pubDate>Mon, 27 Jan 2020 13:20:10 +0000</pubDate><guid>https://bryanavery.co.uk/kubernetes/</guid><description>&lt;h2&gt;Next-Generation Application Development &lt;/h2&gt;&#10;&lt;p&gt;The world of IT infrastructure has evolved dramatically since the days of relying solely on bare metal hardware to support application development. In the early 2000s, a company called VMWare broke the mould, giving rise to virtualization — using an abstraction that makes software (virtual machines) look and behave like hardware. The primary difference between virtualization and bare metal is the inherent benefit of using software to “virtualize” infrastructure. Virtualization offers increased flexibility, scalability, reliability, and often overall capability and performance, all while lowering capital and operational expenses. &lt;/p&gt;</description></item></channel></rss>