<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
  <channel>
    <title>Portainer News and Blog</title>
    <link>https://www.portainer.io/blog</link>
    <description>Latest news and updates from the Portainer team</description>
    <language>en</language>
    <pubDate>Fri, 29 Nov 2024 03:04:35 GMT</pubDate>
    <dc:date>2024-11-29T03:04:35Z</dc:date>
    <dc:language>en</dc:language>
    <item>
      <title>When Kubernetes Feels Like a Burden: Understanding the Challenges and How to Avoid Them</title>
      <link>https://www.portainer.io/blog/when-kubernetes-feels-like-a-burden-understanding-the-challenges-and-how-to-avoid-them</link>
      <description>&lt;p&gt;I &lt;a href="https://blog.stackademic.com/i-stopped-using-kubernetes-our-devops-team-is-happier-than-ever-a5519f916ec0"&gt;recently read&lt;/a&gt; about an organization that abandoned Kubernetes (in their case, in favor of AWS ECS), and how it led to a noticeably happier DevOps team.&lt;/p&gt; 
&lt;p&gt;Stories like this are becoming more common, and it's tempting to see such a move as the only solution when Kubernetes doesn't meet expectations. However, swiftly shifting away from Kubernetes might be more of an emotional response to immediate pain rather than offering strategic, long-term benefits.&lt;/p&gt; 
&lt;p&gt;&lt;span style="font-weight: bold;"&gt;Let's explore why this happens and how organizations can prevent reaching a point where Kubernetes feels more like a burden than a benefit.&lt;/span&gt;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;I &lt;a href="https://blog.stackademic.com/i-stopped-using-kubernetes-our-devops-team-is-happier-than-ever-a5519f916ec0"&gt;recently read&lt;/a&gt; about an organization that abandoned Kubernetes (in their case, in favor of AWS ECS), and how it led to a noticeably happier DevOps team.&lt;/p&gt; 
&lt;p&gt;Stories like this are becoming more common, and it's tempting to see such a move as the only solution when Kubernetes doesn't meet expectations. However, swiftly shifting away from Kubernetes might be more of an emotional response to immediate pain rather than offering strategic, long-term benefits.&lt;/p&gt; 
&lt;p&gt;&lt;span style="font-weight: bold;"&gt;Let's explore why this happens and how organizations can prevent reaching a point where Kubernetes feels more like a burden than a benefit.&lt;/span&gt;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Fwhen-kubernetes-feels-like-a-burden-understanding-the-challenges-and-how-to-avoid-them&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Kubernetes Management Software</category>
      <pubDate>Thu, 28 Nov 2024 20:02:12 GMT</pubDate>
      <author>neil.cresswell@portainer.io (Neil Cresswell, CEO)</author>
      <guid>https://www.portainer.io/blog/when-kubernetes-feels-like-a-burden-understanding-the-challenges-and-how-to-avoid-them</guid>
      <dc:date>2024-11-28T20:02:12Z</dc:date>
    </item>
    <item>
      <title>The Platform Engineering Team - Skills and Experience</title>
      <link>https://www.portainer.io/blog/the-platform-engineering-team-skills-and-experience</link>
      <description>&lt;p&gt;This article is part of our ongoing series on the importance of Platform Engineering. Earlier articles discuss the nature of a &lt;a href="https://www.portainer.io/blog/portainer-the-vending-machine-for-platform-engineering-teams"&gt;Software Delivery Platform&lt;/a&gt; and thoughts on &lt;a href="https://www.portainer.io/blog/excel-in-platform-engineering-by-designing-efficient-self-service-delivery-platforms"&gt;successful Platform Engineering. &lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;In this article we look at the skills and experience that need to come together in the &lt;a href="https://www.portainer.io/solutions/for-platform-engineering"&gt;Platform Engineering&lt;/a&gt; Team. Given the wide range of technologies assembled into a platform, the team responsible will need to maintain (or have access to) an extensive range of skills at a deep level. Generally, combining the skills required with sufficient real-world experience with those skills in a small team is hard.&lt;/p&gt; 
&lt;p&gt;But its possible to get this right, and a great platform team (and a great platform) will revolutionize IT's ability to make a difference&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;This article is part of our ongoing series on the importance of Platform Engineering. Earlier articles discuss the nature of a &lt;a href="https://www.portainer.io/blog/portainer-the-vending-machine-for-platform-engineering-teams"&gt;Software Delivery Platform&lt;/a&gt; and thoughts on &lt;a href="https://www.portainer.io/blog/excel-in-platform-engineering-by-designing-efficient-self-service-delivery-platforms"&gt;successful Platform Engineering. &lt;/a&gt;&lt;/p&gt; 
&lt;p&gt;In this article we look at the skills and experience that need to come together in the &lt;a href="https://www.portainer.io/solutions/for-platform-engineering"&gt;Platform Engineering&lt;/a&gt; Team. Given the wide range of technologies assembled into a platform, the team responsible will need to maintain (or have access to) an extensive range of skills at a deep level. Generally, combining the skills required with sufficient real-world experience with those skills in a small team is hard.&lt;/p&gt; 
&lt;p&gt;But its possible to get this right, and a great platform team (and a great platform) will revolutionize IT's ability to make a difference&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Fthe-platform-engineering-team-skills-and-experience&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Platform Engineering</category>
      <pubDate>Mon, 25 Nov 2024 21:44:58 GMT</pubDate>
      <author>geoff.olliff@portainer.io (Geoff Olliff)</author>
      <guid>https://www.portainer.io/blog/the-platform-engineering-team-skills-and-experience</guid>
      <dc:date>2024-11-25T21:44:58Z</dc:date>
    </item>
    <item>
      <title>Gartner Presentation: Gaining Operational Maturity for Effective Docker/Kubernetes Implementations</title>
      <link>https://www.portainer.io/blog/gartner-presentation-gaining-operational-maturity-for-effective-docker/kubernetes-implementation</link>
      <description>&lt;p&gt;Adopting a containerized platform like Docker/Kubernetes requires significant organizational changes. At Neil's Gartner IOCS presentation in Las Vegas, taking place from December 10-12, 2024, he will explore the essential changes, timelines, and potential challenges required for successful platform operations.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Adopting a containerized platform like Docker/Kubernetes requires significant organizational changes. At Neil's Gartner IOCS presentation in Las Vegas, taking place from December 10-12, 2024, he will explore the essential changes, timelines, and potential challenges required for successful platform operations.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Fgartner-presentation-gaining-operational-maturity-for-effective-docker%2Fkubernetes-implementation&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Kubernetes Management Platform</category>
      <category>Platform Management</category>
      <category>container management</category>
      <category>Kubernetes Management Software</category>
      <category>Platform Engineering</category>
      <pubDate>Fri, 22 Nov 2024 02:39:32 GMT</pubDate>
      <guid>https://www.portainer.io/blog/gartner-presentation-gaining-operational-maturity-for-effective-docker/kubernetes-implementation</guid>
      <dc:date>2024-11-22T02:39:32Z</dc:date>
      <dc:creator>Portainer team</dc:creator>
    </item>
    <item>
      <title>The importance of keeping your Portainer version up to date</title>
      <link>https://www.portainer.io/blog/the-importance-of-keeping-your-portainer-version-up-to-date</link>
      <description>&lt;p&gt;This is a quick reminder about the importance of keeping software up to date. Whether you are using Portainer in your home lab, or managing a large fleet of Kubernetes clusters in the data center or cloud - it’s essential to ensure Portainer and other software you deploy is kept up to date.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;This is a quick reminder about the importance of keeping software up to date. Whether you are using Portainer in your home lab, or managing a large fleet of Kubernetes clusters in the data center or cloud - it’s essential to ensure Portainer and other software you deploy is kept up to date.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Fthe-importance-of-keeping-your-portainer-version-up-to-date&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Portainer New Version</category>
      <category>support</category>
      <category>updates</category>
      <pubDate>Thu, 21 Nov 2024 02:51:56 GMT</pubDate>
      <author>rich.sharples@portainer.io (Rich Sharples)</author>
      <guid>https://www.portainer.io/blog/the-importance-of-keeping-your-portainer-version-up-to-date</guid>
      <dc:date>2024-11-21T02:51:56Z</dc:date>
    </item>
    <item>
      <title>Portainer: The Essential Tool for Docker Swarm Users Facing a Kubernetes Future</title>
      <link>https://www.portainer.io/blog/portainer-the-essential-tool-for-docker-swarm-users-facing-a-kubernetes-future</link>
      <description>&lt;p&gt;Mirantis recently announced the release of &lt;strong&gt;Mirantis Kubernetes Engine (MKE) 4&lt;/strong&gt;, signaling a strategic pivot toward Kubernetes. In their official press release, Mirantis stated:&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;Mirantis recently announced the release of &lt;strong&gt;Mirantis Kubernetes Engine (MKE) 4&lt;/strong&gt;, signaling a strategic pivot toward Kubernetes. In their official press release, Mirantis stated:&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Fportainer-the-essential-tool-for-docker-swarm-users-facing-a-kubernetes-future&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Docker/Swarm</category>
      <category>docker swarm vs kubernetes</category>
      <category>kubernetes vs docker swarm</category>
      <category>Mirantis</category>
      <pubDate>Tue, 19 Nov 2024 21:01:02 GMT</pubDate>
      <author>neil.cresswell@portainer.io (Neil Cresswell, CEO)</author>
      <guid>https://www.portainer.io/blog/portainer-the-essential-tool-for-docker-swarm-users-facing-a-kubernetes-future</guid>
      <dc:date>2024-11-19T21:01:02Z</dc:date>
    </item>
    <item>
      <title>Building a Bare Metal Kubernetes Cluster: Hardware Specifications and Best Practices</title>
      <link>https://www.portainer.io/blog/building-a-bare-metal-kubernetes-cluster-hardware-specifications-and-best-practices</link>
      <description>&lt;p&gt;If you’re gearing up to build a bare metal Kubernetes cluster, you’ve probably got a lot of questions: What kind of servers should I buy? How much storage is enough? How do I make sure a single hardware failure doesn’t ruin my day?&lt;br&gt;&lt;br&gt;Good news—you’re not alone! Let’s walk through the key decisions you’ll face when building your cluster and how to set yourself up for success.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;If you’re gearing up to build a bare metal Kubernetes cluster, you’ve probably got a lot of questions: What kind of servers should I buy? How much storage is enough? How do I make sure a single hardware failure doesn’t ruin my day?&lt;br&gt;&lt;br&gt;Good news—you’re not alone! Let’s walk through the key decisions you’ll face when building your cluster and how to set yourself up for success.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Fbuilding-a-bare-metal-kubernetes-cluster-hardware-specifications-and-best-practices&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <pubDate>Tue, 19 Nov 2024 18:48:55 GMT</pubDate>
      <author>neil.cresswell@portainer.io (Neil Cresswell, CEO)</author>
      <guid>https://www.portainer.io/blog/building-a-bare-metal-kubernetes-cluster-hardware-specifications-and-best-practices</guid>
      <dc:date>2024-11-19T18:48:55Z</dc:date>
    </item>
    <item>
      <title>Filling an Often-Unspoken Gap in Container Management</title>
      <link>https://www.portainer.io/blog/filling-an-often-unspoken-gap-in-container-management</link>
      <description>&lt;p&gt;This article was first published on: &lt;a href="https://www.hostingadvice.com/blog/filling-an-often-unspoken-gap-in-container-management/"&gt;https://www.hostingadvice.com/blog/filling-an-often-unspoken-gap-in-container-management/&lt;/a&gt;&amp;nbsp;&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;This article was first published on: &lt;a href="https://www.hostingadvice.com/blog/filling-an-often-unspoken-gap-in-container-management/"&gt;https://www.hostingadvice.com/blog/filling-an-often-unspoken-gap-in-container-management/&lt;/a&gt;&amp;nbsp;&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Ffilling-an-often-unspoken-gap-in-container-management&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Portainer</category>
      <category>Business case</category>
      <category>container management</category>
      <pubDate>Thu, 07 Nov 2024 03:09:30 GMT</pubDate>
      <guid>https://www.portainer.io/blog/filling-an-often-unspoken-gap-in-container-management</guid>
      <dc:date>2024-11-07T03:09:30Z</dc:date>
      <dc:creator>Guest Post</dc:creator>
    </item>
    <item>
      <title>Does Platform Engineering Leadership Need a Rethink?</title>
      <link>https://www.portainer.io/blog/does-platform-engineering-leadership-needs-a-rethink</link>
      <description>&lt;p&gt;In today’s cloud-native era, a surprising yet common misalignment often arises within &lt;a href="https://www.portainer.io/solutions/for-platform-engineering"&gt;platform engineering&lt;/a&gt; teams: they’re led by someone from an IT infrastructure background rather than someone who has "lived the life" of the platform's primary users—developers.&lt;/p&gt; 
&lt;p&gt;This structure typically leads to a “build and mandate” approach, where the engineering team chooses all the platform tools, the platform is built to their specifications, and its use is enforced through policy.&lt;/p&gt; 
&lt;p&gt;This approach is seen repeatedly, and at the recent Gartner IT Symposium, several talks were given on this topic. The talks explained how Platform Engineering teams need to rethink their behaviors, stop designing to their wishes, and instead design to the explicit needs of their users.&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In today’s cloud-native era, a surprising yet common misalignment often arises within &lt;a href="https://www.portainer.io/solutions/for-platform-engineering"&gt;platform engineering&lt;/a&gt; teams: they’re led by someone from an IT infrastructure background rather than someone who has "lived the life" of the platform's primary users—developers.&lt;/p&gt; 
&lt;p&gt;This structure typically leads to a “build and mandate” approach, where the engineering team chooses all the platform tools, the platform is built to their specifications, and its use is enforced through policy.&lt;/p&gt; 
&lt;p&gt;This approach is seen repeatedly, and at the recent Gartner IT Symposium, several talks were given on this topic. The talks explained how Platform Engineering teams need to rethink their behaviors, stop designing to their wishes, and instead design to the explicit needs of their users.&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Fdoes-platform-engineering-leadership-needs-a-rethink&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Thought Leadership</category>
      <category>Platform Engineering</category>
      <pubDate>Thu, 31 Oct 2024 11:28:26 GMT</pubDate>
      <author>neil.cresswell@portainer.io (Neil Cresswell, CEO)</author>
      <guid>https://www.portainer.io/blog/does-platform-engineering-leadership-needs-a-rethink</guid>
      <dc:date>2024-10-31T11:28:26Z</dc:date>
    </item>
    <item>
      <title>Excel in Platform Engineering by designing efficient self-service delivery platforms</title>
      <link>https://www.portainer.io/blog/excel-in-platform-engineering-by-designing-efficient-self-service-delivery-platforms</link>
      <description>&lt;p&gt;A software development and delivery platform enables an organization to centralize and coordinate the entire software delivery chain. In previous articles, we have idealized this as an IT ‘Vending Machine’ as this idea captures the simplified self-service nature of the ideal software delivery platform. (See the previous &lt;a href="https://www.portainer.io/blog/portainer-the-vending-machine-for-platform-engineering-teams"&gt;article&lt;/a&gt; here)&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;A software development and delivery platform enables an organization to centralize and coordinate the entire software delivery chain. In previous articles, we have idealized this as an IT ‘Vending Machine’ as this idea captures the simplified self-service nature of the ideal software delivery platform. (See the previous &lt;a href="https://www.portainer.io/blog/portainer-the-vending-machine-for-platform-engineering-teams"&gt;article&lt;/a&gt; here)&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Fexcel-in-platform-engineering-by-designing-efficient-self-service-delivery-platforms&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Platform Management</category>
      <category>Portainer Managed Platform Services</category>
      <category>Platform Engineering</category>
      <pubDate>Thu, 31 Oct 2024 01:23:29 GMT</pubDate>
      <author>geoff.olliff@portainer.io (Geoff Olliff)</author>
      <guid>https://www.portainer.io/blog/excel-in-platform-engineering-by-designing-efficient-self-service-delivery-platforms</guid>
      <dc:date>2024-10-31T01:23:29Z</dc:date>
    </item>
    <item>
      <title>DevOps: A Stop-Gap, Not the Future</title>
      <link>https://www.portainer.io/blog/devops-a-stop-gap-not-the-future</link>
      <description>&lt;p&gt;In the world of software, DevOps emerged as a necessary crutch; a way to bridge the gap between the code developers create, and the production deployment of that code. But here’s the reality: DevOps, as most of us know it, is temporary. It exists because the technology we rely on is incomplete, not because it’s the ideal solution. And NO, platform engineering is not the successor to DevOps, as much as marketing strategies would have you believe, they serve different purposes!&lt;/p&gt;</description>
      <content:encoded>&lt;p&gt;In the world of software, DevOps emerged as a necessary crutch; a way to bridge the gap between the code developers create, and the production deployment of that code. But here’s the reality: DevOps, as most of us know it, is temporary. It exists because the technology we rely on is incomplete, not because it’s the ideal solution. And NO, platform engineering is not the successor to DevOps, as much as marketing strategies would have you believe, they serve different purposes!&lt;/p&gt;  
&lt;img src="https://track.hubspot.com/__ptq.gif?a=4731999&amp;amp;k=14&amp;amp;r=https%3A%2F%2Fwww.portainer.io%2Fblog%2Fdevops-a-stop-gap-not-the-future&amp;amp;bu=https%253A%252F%252Fwww.portainer.io%252Fblog&amp;amp;bvt=rss" alt="" width="1" height="1" style="min-height:1px!important;width:1px!important;border-width:0!important;margin-top:0!important;margin-bottom:0!important;margin-right:0!important;margin-left:0!important;padding-top:0!important;padding-bottom:0!important;padding-right:0!important;padding-left:0!important; "&gt;</content:encoded>
      <category>Thought Leadership</category>
      <pubDate>Wed, 30 Oct 2024 15:13:23 GMT</pubDate>
      <author>neil.cresswell@portainer.io (Neil Cresswell, CEO)</author>
      <guid>https://www.portainer.io/blog/devops-a-stop-gap-not-the-future</guid>
      <dc:date>2024-10-30T15:13:23Z</dc:date>
    </item>
  </channel>
</rss>
