Virtual infrastructure has a lot of advantages, but one of the biggest time savers is being able to provision new virtual machines quickly from a template. As part of this series we’ve covered, how to deploy harvester, how to setup a new virtual network , how to create a new virtual machine, and how to backup and restore VMs. In this post we’ll take a look at how we can create templates and deploy harvester VMs from templates. ...
In our previous posts we setup a Harvester cluster in our lab, configured the network, and deployed our first VM. Here we will explore the backup and restore options available to us from the Harvester console. If you’re new to running virtual machines on Kubernetes, you’re probably questioning a few things, like will your current VM backup tool work? The answer is maybe, but only if it is able to backup a container since our VMs are now wrapped inside of a Kubernetes Pod thanks to Kubevirt. There are several options out there (I work for one of those companies myself) but this post only focuses on whats built into the Harvester solution. ...
I have a very soft spot in my heart for VMware. Pretty early on in my career when I was a System Administrator I got the opportunity to convert my companies physical infrastructure to a virtual infrastructure on VMware vSphere. The version of VMware we moved to, is not relevant to this discussion other than to show how truly old I am, and in order to save the parties involved some embarrassment we’ll ignore this implementation detail. ...
During the previous posts in this series, we deployed a Harvester cluster, setup virtual networks to segment traffic, and deployed our first virtual machine. So far this has been a pretty good experience, but most of my day job requires me to do a lot of work on containers so I’d like to have Kubernetes clusters at home. Of course I could deploy a bunch of VMs for a new Kubernetes cluster, but Harvester is built on top of Kubernetes already. So this post will show us how we can connect Rancher to our Harvester cluster so we can use the underlying Kubernetes cluster that Harvester runs on to run our own containers. ...
In the previous posts, we setup the Harvester cluster and optionally added a virtual machine network and some cluster configs. In this post we’ll deploy our first Harvester virtual machine on our cluster. Before we do this, I wanted to point out that we’ve gotten to this point really without ever needing Kubernetes. If you’re paying close attention to the screens that have been showing up in the GUI, you might notice things like a namespace or labels or annotations that are clearly Kubernetes references. Even still, there’s really nothing in the steps up to this point where it would’ve required any Kubernetes experience at all. We’ll continue that trend as we build our first virtual machine. ...
In the first post in this series I deployed a Harvester cluster to my home lab servers. Before I get into deploying virtual machines though, I want to make some common configuration updates to my cluster. For instance, I want my virtual machine network traffic to be placed on a different network. Placing the small amount of network traffic that my virtual machines might be using on their own NIC is probably not necessary in my lab. But I wanted to build the lab in a way that somewhat mimics the way virtual machines are deployed in production environments so I can see how it works. When deploying VMware ESXi hosts, I would commonly have several virtual machine networks on their own NIC, each on their own VLAN. In this post we’ll deploy a Harvester virtual machine network. ...
The installation of Harvester starts with deploying your nodes. This process would be similar to deploying ESXi hosts in a VMware deployment. To start the process, download the latest stable harvester release from their github repository. You can then mount this ISO file from your bare metal server. Create the First Harvester Node in a Cluster After booting to the iso choose the version of Harvester to deploy from their GRUB list. In this example we’ll be using v1.2.1. Since this is the first node in my cluster, I will choose to create a new cluster, and then hit enter. ...
Yes, that’s right, this website is now 10 years old, and while there is no cake or ice cream for this celebration, I thought I’d take a second to reflect on what this website, and the 550 blog posts in it, have meant to me personally. This site has in many ways chronicled my technology career, starting when I was a System Administrator, trying to learn Virtualization, up until now. I had no idea what I wanted this site to be, but I knew that I’d gained so much help from other bloggers in my day to day work, that I wanted to help out somebody myself. It seemed like the leave-a-penny / take-a-penny tray at a store. I didn’t want to only be taking penny’s out of that thing, sometimes you’ve got to be the one putting pennies in. That’s how I felt about my blog when I started. ...
Early this year I saw a challenge drop in my inbox for VMware vExperts to deploy a Plex server with Tanzu Community Edition (TCE). I hadn’t gotten to try out TCE yet, and had never messed with Plex so this sounded like a fun adventure. The goal was to architect an entire solution as though this Plex server was going to be a production app that a company might run their business off of. Which means, that I needed to not only get the thing working, but start making some steps to operationalize it. You know of course that production systems come with security, observability, auto-scaling, an incident response routine, etc. Well, this is my home lab so we’ll have to assume that this is my minimum viable product, because as you’ll see, I could still put a lot of work in here. ...
I was messing around in my vSphere home lab and wanted to try out the new Tanzu Community Edition that was recently announced. After getting up to speed on some of the documentation, I tried the installation out in my vSphere 7 lab. There were a couple of notes that I think will help some other people get started with their installation. TCE logo Bootstrapping on MacBook The installation on my MacBook kept failing when trying to deploy the management cluster in my vSphere environment. It turned out that the version of docker I was using was leveraging cgroupsv2 which caused an issue with the bootstrap process. You can read more info about the fixes being worked on in this GitHub issue. To workaround this issue, I pre-deployed a kind cluster using the command: ...