<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
  <channel>
    <title>VPA on alexos.dev</title>
    <link>https://alexos.dev/tags/vpa/</link>
    <description>Recent content in VPA on alexos.dev</description>
    <generator>Hugo</generator>
    <language>en-gb</language>
    <lastBuildDate>Sun, 21 May 2023 19:00:00 -0100</lastBuildDate>
    <atom:link href="https://alexos.dev/tags/vpa/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>GKE Compute Cost Comparisons In Small Clusters</title>
      <link>https://alexos.dev/2023/05/21/gke-compute-cost-comparisons-in-small-clusters/</link>
      <pubDate>Sun, 21 May 2023 19:00:00 -0100</pubDate>
      <guid>https://alexos.dev/2023/05/21/gke-compute-cost-comparisons-in-small-clusters/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://alexos.dev/images/savings.jpg?width=800px&amp;amp;classes=shadow&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;p&gt;&#xA;          &lt;a href=&#34;https://unsplash.com/photos/SoT4-mZhyhE&#34;&gt;Photo by Micheile Henderson on Unsplash&lt;/a&gt;&lt;/p&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;I&amp;rsquo;ve been running a short-term experiment across the GKE Compute options within my &amp;ldquo;Home Lab&amp;rdquo; &lt;em&gt;(read: GCP-hosted Google Kubernetes Engine)&lt;/em&gt; with a view to optimise for a balance between ease of operation and cost efficiency. If that sounds useful to you, then by all means read on!&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;Let&amp;rsquo;s dive right in with the Billing data. The chart below shows the view of costs over the course of my two-month experiment for this small GKE Cluster. I&amp;rsquo;ll be stepping across this graph to detail each experiment I ran and what led to these outcomes, as well as some of the trade-offs along the way.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Squeezing GKE System Resources In Small Clusters</title>
      <link>https://alexos.dev/2019/09/28/squeezing-gke-system-resources-in-small-clusters/</link>
      <pubDate>Sat, 28 Sep 2019 18:00:00 -0100</pubDate>
      <guid>https://alexos.dev/2019/09/28/squeezing-gke-system-resources-in-small-clusters/</guid>
      <description>&lt;figure&gt;&lt;img src=&#34;https://alexos.dev/images/squeeze-1.jpg?width=600px&amp;amp;classes=shadow&#34;&gt;&lt;figcaption&gt;&#xA;      &lt;p&gt;&#xA;          &lt;a href=&#34;https://unsplash.com/photos/cDwZ40Lj9eo&#34;&gt;Photo by Davide Ragusa on Unsplash&lt;/a&gt;&lt;/p&gt;&#xA;    &lt;/figcaption&gt;&#xA;&lt;/figure&gt;&#xA;&#xA;&lt;p&gt;&lt;strong&gt;Spoiler Alert!&lt;/strong&gt; This blog is &lt;em&gt;really&lt;/em&gt; about Vertical Pod Autoscaling and patching of &lt;code&gt;kube-system&lt;/code&gt; workloads in GKE. It just might not sound like it at the start &amp;#x1f604; If you&amp;rsquo;re not interested in how I got there and just want to jump to the good stuff - I&amp;rsquo;ve summarised it at the &lt;a href=&#34;#in-summary&#34;&gt;bottom of the post&lt;/a&gt;.&lt;/p&gt;&#xA;&lt;hr&gt;&#xA;&lt;p&gt;So, this all started because I wanted to try out Elasticsearch. I&amp;rsquo;m not the biggest fan of GCP&amp;rsquo;s Stackdriver Logging, and I wanted to poke around with some alternatives. I have a &amp;ldquo;personal&amp;rdquo; GKE cluster that I use to run a few websites (including this blog!), and where I also experiment with these sort of things outside of work. Should be straight-forward I thought to myself. Sure, Elastic is Java - but I don&amp;rsquo;t need it to do that much, I&amp;rsquo;ll just shrink it down enough that it&amp;rsquo;ll start up ok, play around a bit, and then maybe see if I want to do more with it or sign up to a managed logging service instead.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
