<?xml version="1.0" encoding="utf-8" standalone="yes"?>
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom" xmlns:content="http://purl.org/rss/1.0/modules/content/">
  <channel>
    <title>Resize on The IT Hollow</title>
    <link>https://theithollow.com/tags/resize/</link>
    <description>Recent content in Resize on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Wed, 09 Dec 2020 15:05:00 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/tags/resize/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Resizing Tanzu Kubernetes Grid Cluster Nodes</title>
      <link>https://theithollow.com/2020/12/09/resizing-tanzu-kubernetes-grid-cluster-nodes/</link>
      <pubDate>Wed, 09 Dec 2020 15:05:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/12/09/resizing-tanzu-kubernetes-grid-cluster-nodes/</guid>
      <description>&lt;p&gt;Have you ever missed when trying to properly size an Kubernetes environment? Maybe the requirements changed, maybe there were wrong assumptions, or maybe the project took off and it just needs more resources. Under normal circumstances, I might suggest to you to build a new Tanzu Kubernetes Grid (TKG) cluster and re-deploy your apps. Unfortunately, as much as I want to treat Kubernetes clusters as ephemeral, they can&amp;rsquo;t always be treated this way. If you need to resize your TKG nodes without re-deploying a new cluster, then keep reading.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tanzu Mission Control - Resize Clusters</title>
      <link>https://theithollow.com/2020/03/10/tanzu-mission-control-resize-clusters/</link>
      <pubDate>Tue, 10 Mar 2020 18:00:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/03/10/tanzu-mission-control-resize-clusters/</guid>
      <description>&lt;p&gt;A pretty common task that a Kubernetes administrator must do is to resize the cluster. We need more nodes to handle more workloads, or we&amp;rsquo;ve overprovisioned a cluster and are trying to save costs. This usually took some custom automation scripts such as node autoscaler, or it was done manually based on request.&lt;/p&gt;
&lt;p&gt;Tanzu Mission Control can resize our cluster very simply from the TMC portal.&lt;/p&gt;
&lt;h2 id=&#34;scale-out-a-cluster&#34;&gt;Scale Out a Cluster&lt;/h2&gt;
&lt;p&gt;Within the TMC Portal, find the cluster that needs to be resized. Within the cluster screen, find the &amp;ldquo;Node pools&amp;rdquo; menu. Node pools define the worker nodes that are part of the Kubernetes cluster thats been deployed.&lt;/p&gt;</description>
    </item>
  </channel>
</rss>
