<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>Autoscaling on Eric Irwin</title><link>http://ericirwin.io/tags/autoscaling/</link><description>Recent content in Autoscaling on Eric Irwin</description><generator>Hugo</generator><language>en-us</language><managingEditor>Eric.Irwin@gmail.com (Eric Irwin)</managingEditor><webMaster>Eric.Irwin@gmail.com (Eric Irwin)</webMaster><lastBuildDate>Mon, 10 Jan 2022 00:00:00 +0000</lastBuildDate><atom:link href="http://ericirwin.io/tags/autoscaling/index.xml" rel="self" type="application/rss+xml"/><item><title>Custom Autoscaling for GitLab Kubernetes Executors</title><link>http://ericirwin.io/posts/custom-autoscaling-for-gitlab-kubernetes-executors/</link><pubDate>Mon, 10 Jan 2022 00:00:00 +0000</pubDate><author>Eric.Irwin@gmail.com (Eric Irwin)</author><guid>http://ericirwin.io/posts/custom-autoscaling-for-gitlab-kubernetes-executors/</guid><description>&lt;p&gt;I recently had the opportunity to share some really interesting work that our team at Quantum Metric was doing to improve the performance and reliability of our GitLab CI pipelines.&lt;/p&gt;
&lt;p&gt;The intention of this article is to provide an overview of why and how our team decided to implement our own custom autoscaling for our GitLab CI jobs running on Kubernetes.&lt;/p&gt;
&lt;h2 id="introduction"&gt;Introduction&lt;/h2&gt;
&lt;p&gt;Our engineering organization has evolved significantly over the past three years. We have experienced rapid growth within our teams as well as our customer base and we continue to improve how we are delivering value quickly and reliably to our customers.&lt;/p&gt;</description></item></channel></rss>