{"id":567,"date":"2024-12-20T17:45:57","date_gmt":"2024-12-20T16:45:57","guid":{"rendered":"https:\/\/zerobotics.de\/blog\/?p=567"},"modified":"2024-12-20T17:45:57","modified_gmt":"2024-12-20T16:45:57","slug":"vsphere-iaas-control-plane-or-vsphere-kubernetes-service-installation-of-a-new-tkg-service-version","status":"publish","type":"post","link":"https:\/\/zerobotics.de\/blog\/en\/vsphere-iaas-control-plane-or-vsphere-kubernetes-service-installation-of-a-new-tkg-service-version\/","title":{"rendered":"vSphere IaaS Control Plane or vSphere Kubernetes Service: Installation of a new TKG Service version"},"content":{"rendered":"Reading Time<\/span> 3<\/span> Minutes<\/span><\/span>\n

With the release of vSphere 8U3, vSphere with Tanzu<\/strong> was not only renamed (multiple times) but also a step was taken to „decouple“ TKGs<\/strong> from the vCenter version.<\/p>\n\n\n\n

Until then, TKGs<\/strong> and vSphere with Tanzu<\/strong> were considered a single entity and thus synonymous with each other.
One disadvantage of this was that the available Kubernetes versions for the Tanzu Kubernetes clusters (i.e., the „child“ clusters of the Supervisor Cluster) depended on the version of the vCenter Server.<\/p>\n\n\n\n

If you wanted to use a current k8s release, the first step was inevitably to update the vCenter.<\/p>\n\n\n\n

Since vSphere 8U3, in addition to the IaaS Control Plane<\/s> vSphere Kubernetes Service<\/strong>, which provides the Supervisor, there is now also a TKGs Service<\/strong> responsible for the Tanzu Kubernetes Clusters (TKC)<\/strong>. Since this can be updated independently, it allows quicker and easier access to current k8s releases \ud83e\udd73\ud83e\udd73\ud83e\udd73<\/p>\n\n\n\n

In the following, I\u2019ll briefly show how to update this crazy thing .<\/p>\n\n\n\n\n\n\n\n

First, let\u2019s check which TKGs Service version is currently running.
To do this, navigate through the vCenter: Workload Management >> Supervisors >> the relevant Supervisor >> Configure >> Supervisor Services >> Overview<\/em>.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Deep down in some Supervisor Menus we find the current version.<\/figcaption><\/figure>\n\n\n\n

In my case, the TKGs Service is already running on version 3.1.1, which came with vCenter 8U3b.
However, an independent new version (v3.2.0) has since been released, which can be manually downloaded and added.<\/p>\n\n\n\n

Why is this cool?
Because this new version, aside from some bug fixes, of course, also enables new features and options, such as support for Kubernetes 1.31, Windows Server as worker nodes (WTF?!), adjustments to the API (bye bye Tanzu naming convention), and more…
(these are the Release Notes<\/a>, check for yourself!)<\/p>\n\n\n\n

<\/div>\n\n\n\n

Good example: While Release 1.31.1 exists, I can’t use it without the Service Update:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Before 3.2.0<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

As mentioned above, I don’t need to update the vCenter for this; I only need to update the service.
To install the new version, navigate to Workload Management >> Services >> Tanzu Kubernetes Grid Service<\/em><\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Find the TKGs Service in the vCenter<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

First, let\u2019s check out which versions are available under „Manage Versions“:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n
<\/div>\n\n\n\n

As you can see, there are two versions listed here. Version 3.1.1 became available automatically after updating vCenter to 8U3b, and that\u2019s the one I\u2019ve already got running.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

The new version 3.2.0 doesn\u2019t show up here yet, so you\u2019ll need to grab it yourself. You can find everything you need here:
vSphere Supervisor Services<\/a><\/p>\n\n\n\n

<\/div>\n\n\n\n

So i get myself this piece of cake…sorry, i meant YAML…<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

…and upload it here under „Add New Version<\/em>„:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

…“Upload<\/em>„…<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

…“Finish<\/em>„.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n

A cute little green box confirms that I can now apply the new version to my Supervisor:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n
<\/div>\n\n\n\n

When I check under „Manage Versions<\/em>“ again, it\u2019s now showing up there too:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button><\/figure>\n\n\n\n
<\/div>\n\n\n\n

Alright, back to my Supervisor >> Configure >> Supervisor Services Overview<\/em>, then select the Tanzu Kubernetes Grid Service<\/em> on the right and click Manage<\/em>:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

…selecting the new version for my Supervisor…<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

…short review, aha, yes, looks good, Finish<\/em>:<\/p>\n\n\n\n

\"\"<\/figure>\n\n\n\n

It\u2019s doing its thing now and even renamed my service to „Kubernetes Service“:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Doing something…<\/figcaption><\/figure>\n\n\n\n

Then, suddenly, this error popped up for a moment *gulp*<\/em>:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
oh no, please no error!<\/figcaption><\/figure>\n\n\n\n

But a few minutes later, it was gone again (probably due to my lab\u2019s hyper performance) and everything was done shortly after:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
hey, the name is not Tanzu anymore (R.I.P \ud83e\udea6)<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

In „Manage Versions“<\/em>, we can then clean up a bit by first disabling the versions we don\u2019t want anymore and then deleting them:<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
Getting rid of the old stuff…<\/figcaption><\/figure>\n\n\n\n
<\/div>\n\n\n\n

And now I can access the latest Kubernetes release (in this case, 1.31.1) for my workload clusters WITHOUT having to update my vCenter or Supervisor Cluster first \ud83d\udc4d. Plus, thanks to the API changes, I\u2019m already being warned that „tanzukubernetesrelease“ is old news and shouldn\u2019t be used anymore.<\/p>\n\n\n\n

\"\"\n\t\t\t\n\t\t\t\t\n\t\t\t<\/svg>\n\t\t<\/button>
After installing 3.2.0<\/figcaption><\/figure>\n\n\n\n

Conclusion:<\/strong>
VMware by Broadcom is sticking to its plan and making its Kubernetes integration more flexible and independent from the Tanzu division within vSphere\/VCF.<\/p>\n\n\n\n

Where vCenter updates were previously required to access new features, functionalities, and versions for the Supervisor Cluster and Workload Clusters, now it\u2019s enough to just perform a TKG Service update.<\/p>\n\n\n\n

<\/div>\n","protected":false},"excerpt":{"rendered":"

Reading Time<\/span> 3<\/span> Minutes<\/span><\/span>With the release of vSphere 8U3, vSphere with Tanzu was not only renamed (multiple times) but also a step was taken to „decouple“ TKGs from the vCenter version. Until then, TKGs and vSphere with Tanzu were considered a single entity and thus synonymous with each other.One disadvantage of this was that the available Kubernetes versions […]<\/p>\n","protected":false},"author":1,"featured_media":548,"comment_status":"closed","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[118,121,30],"tags":[],"class_list":["post-567","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-iaas-control-plane-en","category-tanzu-en","category-vmware-en"],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/posts\/567","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/comments?post=567"}],"version-history":[{"count":4,"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/posts\/567\/revisions"}],"predecessor-version":[{"id":573,"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/posts\/567\/revisions\/573"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/media\/548"}],"wp:attachment":[{"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/media?parent=567"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/categories?post=567"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/zerobotics.de\/blog\/wp-json\/wp\/v2\/tags?post=567"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}