Kubernetes is the de facto standard and fast-growing container management platform that enables a multitude of new, scalable, and resilient cloud native applications to thrive.
These container-based applications typically reside on a limited number of worker nodes that comprise a Kubernetes cluster. These clusters typically have one or three management nodes, depending on availability requirements.
Above that, you ideally have an orchestration service that orchestrates and lifecycles these guest clusters to standardize and automate. In vSphere with Tanzu these are called supervisor clusters that are built as the bridge between classical virtualization and the new cloud native realm. There is a lot to manage in the overall.
Google sponsored project Borg to the Cloud Native Computing Foundation (CNCF) in 2016. Consequently, Kubernetes became one of the most thriving open-source projects in the history of IT. After the usual movement through the hype cycle of Container Orchestration technologies, K8 is now mature and ready for enterprise grade production environments.
Moreover, many platforms like VMware with Tanzu, Red Hat and OpenShift or AKS by Azure, exist. These cloud providers offer their flavored K8s products, that fit into their ecosystem and heavily rely on automation and security.
Now, companies that adopted the K8s stack and started operating microservices arrive at new challenges. For example, managing multi tenancy and multiple cluster environments.
So, Tanzu Mission Control (TMC) is a relatively new product which offers diverse functions to supervise these environments in a single pane of glass. It reached General Availability on June 4, 2021. … and I already stressed that out, but more about hands-on soon.
vSphere with Tanzu, the easy and integrated way to use Kubernetes in Enterprise environments, is getting a lot of traction currently. One of the main benefits of this solution is the transparent way to consume already existing storage resources.
So, this article describes the different possibilities and essential features that enable consuming persistent storage in your container applications based on Kubernetes.
Top Trends of Our Customers Result of my presentation poll – interface workshop 02/22
The Tanzu Way
In fact, Tanzu arrives in different editions. Enterprise Plus is mandatory for your ESXi base cluster. In addition, an add-on, with currently three available Tanzu editions: Basic, Standard and Advanced, makes everything possible. Then you enable Tanzu Workload Management in vCenter.
Thus, some requirements exist, like a supported & configured networking and load balancing solution. Furthermore, a lot of different architectural possibilities and design decisions have to be resolved.
Anyway, you need storage resources to provide persistent storage for on one hand your supervisor cluster and on the other your workload clusters for your modern application landscape.
Tough Tanzu means you can operate virtual machines besides Kubernetes clusters with the same interface, resources, and transparency like you have done it for years. Finally, this is the way to your on-premise hybrid cloud environment.
vSphere Storage Resources
Basically, all types of shared storage in vSphere are also supported in Tanzu. On one hand, you got the NFS Shares (NAS), FC or iSCSI LUNs (SAN), the exotic vVOLs (SAN/NAS) and on the other the fully integrated way via. vSAN (HCI) with special features on top.
A mandatory part for usage of storage in Tanzu is the proper configuration of a Storage Policy. Depending on the type of storage, you can utilize various adjustable policy-based features like IOPs limits.
Of course, you can create countless different storage policies and create your own schema to provide an exact fulfillment of your requirements. Besides, people like to call it Gold, Silver, and Bronze depending on the performance and availability demands.
Provisioning Storage for Tanzu Guest Cluster
The consumption of storage in Kubernetes is straightforward through the abstraction and automatic conversion of storage policies to storage classes.
Storage classes are what you consume in Kubernetes to provide your persistent volumes through persistent volume claims.
Actually, vSphere provides an effortless way to group workload clusters into vSphere Namespaces. The vSphere admin has full governance and furnishes these namespaces with the appropriate resources for the developer.
Besides access policies through vSphere single sign on (SSO) you also attach your storage policies to the vSphere namespaces, and you are ready to rock.
Homelab: Fresh Namespace “test-01” with two policies attached (red-box)
Maximum Integration with vSAN
Maximum integration and availability through awesome features that come with vSphere and vSAN 7 U3!
vSAN is now capable of supplying NFS and SMB file services in an easy and automated way. These file services now are fully integrated in vSphere with Tanzu. They provide read write many volumes (RWX) for container services.
This is a giant leap forward to make the life cushier for the vSphere admin and the developer. Different containers can read and write into the same persistent volume (PV).
Moreover, vSAN stretched cluster / fault domain functionality works for Kubernetes environments and is partially supported. VMware’s R&D is working heavily in the background, designing and providing new features as soon as possible.
Homelab: Workload enabled vSAN Stretched Cluster with red annotations
Media, Resources, and Call to Action
Do you want to hear more? In September 2021, we launched our Podcast (German):
Thanks to the best colleagues in the world: Jan Philip Hoepfner, Daniel Rusche and many more from Medialine Group, to make that possible.
To sum up, Tanzu is one of our core topics, and we already got different episodes. More in planning and incoming. Every 14 days, a new episode guaranteed.
Find us on all major podcast platforms: Apple, Amazon, Google, …
Finally, we appreciate your feedback, comments, and your thumbs up on our various platforms.
Furthermore, see me and my great fellow workers speaking at our free interface workshop in April 2022. Dresden, Berlin, and Remote attendance possible :).
Gladly I could earn the Tanzu Specialist Badge today. This article shares my experience with the vSphere with Tanzu Specialist remote exam and hopefully motivates other to try it out as well.
So, this new type of exam will test you on your knowledge in various domains, vSphere, vSphere with Tanzu, NSX-T and Kubernetes.
Rapid change is among us. We are flooded with new concepts and technologies. This article will dive into the new possibilities to host cloud native workloads in the vSphere environment. Actually, VMware released a new suite of products in April 2020 named Tanzu.
Finally, I finished designing and implementing my new home-lab environment based on VMware vSphere.
Thus, I could deploy and test many new VMware products and features like vSphere 7 U2, vSAN, vRealize Automation 8.3 and vRealize Orchestrator 8.3. Meanwhile, I feel in love with infrastructure as code. So, I created and edited several JSON & YAML files to get my infrastructure up and running.
In this week the time came to build up a nested environment that is capable to run vSphere with Kubernetes.
Thanks to vSphere 7 U2 Tanzu is now supported with three different load balancing setups: NSX-T the most expensive, HA proxy which is free and new in U2, NSX advanced load balancer essentials free as well. Without load balancing neither Container nor Kubernetes will work properly.
My choice for lab was HA proxy because my nested environment was built stable & lightweight on vSphere 7 U1.
Finally, five years after the release of vSphere 6 in 2015, the time has come for the next level of the first class enterprise hypervisor ESXi and it’s management environment VCenter Server. After several announcements, the new version 7.0 GA was released, public downloadable, at beginning of April 2020. Meanwhile there was a lot of time to stage the first upgrades and evaluate the new features. Read on and check out my insights…
