<?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>Tanzu-Mission-Control on The IT Hollow</title>
    <link>https://theithollow.com/categories/tanzu-mission-control/</link>
    <description>Recent content in Tanzu-Mission-Control on The IT Hollow</description>
    <generator>Hugo</generator>
    <language>en-us</language>
    <lastBuildDate>Tue, 10 Mar 2020 18:00:00 +0000</lastBuildDate>
    <atom:link href="https://theithollow.com/categories/tanzu-mission-control/index.xml" rel="self" type="application/rss+xml" />
    <item>
      <title>Tanzu Mission Control - Access Policies</title>
      <link>https://theithollow.com/2020/03/10/tanzu-mission-control-access-policies/</link>
      <pubDate>Tue, 10 Mar 2020 18:00:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/03/10/tanzu-mission-control-access-policies/</guid>
      <description>&lt;p&gt;Controlling access to a Kubernetes cluster is an ongoing activity that must be done in conjunction with developer needs and is often maintained by operations or security teams. Tanzu Mission Control (TMC) can help use setup and manage these access policies across fleets of Kubernetes clusters, making everyone&amp;rsquo;s life a little bit easier.&lt;/p&gt;
&lt;h2 id=&#34;setup-users&#34;&gt;Setup Users&lt;/h2&gt;
&lt;p&gt;Before we can assign permissions to a user or group, we need to have a user or group to assign these permissions. By logging into the VMware Cloud Services portal (cloud.VMware.com) and going to the Identity and Access Management Tab we can create and invite new users. You can see I&amp;rsquo;ve created a user.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tanzu Mission Control - Attach Clusters</title>
      <link>https://theithollow.com/2020/03/10/tanzu-mission-control-attach-clusters/</link>
      <pubDate>Tue, 10 Mar 2020 18:00:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/03/10/tanzu-mission-control-attach-clusters/</guid>
      <description>&lt;p&gt;What do you do if you&amp;rsquo;ve already provisioned some Kubernetes clusters before you got Tanzu Mission Control? Or maybe you&amp;rsquo;re inheriting some new clusters through an acquisition? Or a new team came on board and were using their own installation? Whatever the case, Tanzu Mission Control will let you manage a conformant Kubernetes cluster but you must first attach it.&lt;/p&gt;
&lt;h2 id=&#34;attach-an-existing-cluster&#34;&gt;Attach An Existing Cluster&lt;/h2&gt;
&lt;p&gt;For this example, I&amp;rsquo;ll be attaching a pre-existing Kubernetes cluster on vSphere infrastructure. This cluster was deployed via kubeadm as documented in this previous article about deploying &lt;a href=&#34;https://theithollow.com/2020/01/08/deploy-kubernetes-on-vsphere/&#34;&gt;Kubernetes on vSphere&lt;/a&gt;.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tanzu Mission Control - Cluster Upgrade</title>
      <link>https://theithollow.com/2020/03/10/tanzu-mission-control-cluster-upgrade/</link>
      <pubDate>Tue, 10 Mar 2020 18:00:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/03/10/tanzu-mission-control-cluster-upgrade/</guid>
      <description>&lt;p&gt;Kubernetes releases a new minor version every quarter and updating your existing clusters can be a chore. With updates coming at you pretty quickly and new functionality being added all the time, having a way to upgrade your clusters is a must, especially if you are managing multiples of clusters. Tanzu Mission Control can take the pain out of upgrading these clusters.&lt;/p&gt;
&lt;p&gt;It should be mentioned that the cluster upgrade procedure only works for clusters that were previously deployed through Tanzu Mission Control. If an existing cluster is attached to TMC after deployment, these cluster lifecycle steps won&amp;rsquo;t work.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tanzu Mission Control - Conformance Tests</title>
      <link>https://theithollow.com/2020/03/10/tanzu-mission-control-conformance-tests/</link>
      <pubDate>Tue, 10 Mar 2020 18:00:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/03/10/tanzu-mission-control-conformance-tests/</guid>
      <description>&lt;p&gt;No matter what flavor of Kubernetes you&amp;rsquo;re using, the cluster should have some high level of common functionality with the upstream version. To ensure this is the case Kubernetes conformance tests can validate your clusters. These tests are run by Sonobuoy which is an open source community standard. Tanzu Mission Control can run these tests on your clusters to ensure this conformance. They are a great way to make sure your cluster was installed, configured and operating properly.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tanzu Mission Control - Deploying Clusters</title>
      <link>https://theithollow.com/2020/03/10/tanzu-mission-control-deploying-clusters/</link>
      <pubDate>Tue, 10 Mar 2020 18:00:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/03/10/tanzu-mission-control-deploying-clusters/</guid>
      <description>&lt;p&gt;I&amp;rsquo;ve written about deploying clusters in the past, but if you are a TMC customer, those steps can be skipped altogether. TMC will let us deploy a Kubernetes cluster and add it to management, all from the GUI or CLI.&lt;/p&gt;
&lt;p&gt;For this example, I&amp;rsquo;ll create a new Kubernetes cluster within my AWS account. Before we setup the cluster, we need to configure access to our AWS Account so that TMC can manage resources for us.&lt;/p&gt;</description>
    </item>
    <item>
      <title>Tanzu Mission Control - Namespace Management</title>
      <link>https://theithollow.com/2020/03/10/tanzu-mission-control-namespace-management/</link>
      <pubDate>Tue, 10 Mar 2020 18:00:00 +0000</pubDate>
      <guid>https://theithollow.com/2020/03/10/tanzu-mission-control-namespace-management/</guid>
      <description>&lt;p&gt;When we need to segment resources within a Kubernetes cluster, we often use a &lt;a href=&#34;https://theithollow.com/2019/02/06/kubernetes-namespaces/&#34;&gt;namespace&lt;/a&gt;. Namespaces can be excellent resources to create a boundary for either networking, role based access, or simply for organizational purposes. It may be common to have some standard namespaces across all of your clusters. Maybe you have corporate monitoring standards and the tools live in a specific namespace, or you always have an ingress namespace thats off limits to developers or something. Managing namespaces across cluster could be tedious, but Tanzu Mission Control lets us manage these namespaces centrally from the TMC console.&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>
