diff --git a/content/posts/upgrading-standalone-vsphere-host-with-esxcli/index.md b/content/posts/upgrading-standalone-vsphere-host-with-esxcli/index.md
index 0adeaae..509b9f8 100644
--- a/content/posts/upgrading-standalone-vsphere-host-with-esxcli/index.md
+++ b/content/posts/upgrading-standalone-vsphere-host-with-esxcli/index.md
@@ -21,6 +21,12 @@ tags:
   - vsphere
 comment: true # Disable comment if false.
 ---
+You may have heard that there's a new vSphere release out in the wild - [vSphere 8, which just reached Initial Availability this week](https://advocacy.vmware.com/Article/Redirect/9cfbc1b1-207f-4885-a520-cc0bfafcd6c0?uc=197618&g=2d17264e-593a-492d-8d91-3a2155e835f1&f=3104867). Upgrading the vCenter in my single-host homelab is a very straightforward task, and using the included Lifecycle Manager would make quick work of patching a cluster of hosts... but things get a little trickier with a single host. I could write the installer ISO to a USB drive, boot the host off of that, and go through the install interactively, but what if physical access to the host is kind of inconvenient?
+
+The other option for upgrading a host is using the `esxcli` command to apply an update from a `depot.zip`. It's a pretty easy solution (and can even be done remotely, such as when connected to my homelab via the [Tailscale node running on my Quartz64 ESXi-ARM host](esxi-arm-on-quartz64/#installing-tailscale)) *but I always forget the commands.*
+
+So here's quick note on how I upgraded my lone ESXi to the new ESXi 8 IA release so that maybe I'll remember how to do it next time and won't have to go [Neeva](https://neeva.com)'ing for the answer again.
+
 
 ```shell
 ; esxcli system maintenanceMode set -e true