Kubernetes 101 series retrospective, and a new book!

Early in 2020, I kicked off the Ansible 101 live streaming series. I wrote an Ansible 101 retrospective post and decided to give it another go, this time covering Kubernetes.

Starting late in 2020 and wrapping things up today, I streamed a new 10-episode series, Kubernetes 101 (the first episode is embedded below).

This time I had an official series sponsor, I built a custom website and dedicated GitHub repo for the project, and poured in 3-4x more hours per episode... which resulted in a marginal increase in viewership, but not nearly as much as I'd hoped going into my second tech livestream series.

Let's dive into some numbers:


Here's a breakdown of watch hours per episode (through the first nine):

Watch Hours Per Episode for Kubernetes 101

You can see a pretty big drop-off after the first episode. I've found that to be typical with any kind of episodic content on YouTube (I see a similar thing for my Raspberry Pi Cluster series and my Drupal 7 to 8 Upgrade series. YouTube seems to promote the first episode a lot, and barely even suggests any others.

Here are a few other relevant stats a couple months in (note that these numbers will go up over time—these are as of Feb 9, 2021):

  • Kubernetes 101 episodes have had 124,500 views
  • People have watched for 23,684 hours
  • YouTube AdSense revenue totaled around *$699.33**

Compare that to the Ansible 101 live streaming series retrospective (when my YouTube channel was around 10x smaller). The revenue is appreciably higher, but so was the number of hours I worked prepping these ten episodes!

Is it worth it (money-wise)?

Each video averaged $69 in ad revenue (nice), and required around 10 hours of work to produce (including the time spent live streaming each Wednesday). By ad revenue alone, the total hourly wage equivalent is $7/hour.

Sponsorship bumps that number a bit, but we're still talking less than a quarter my consulting rate.

That number also doesn't account for the ~$1,000 of extra equipment I use to live stream. As I've been transitioning from blogging to YouTube, I've learned that episodic or open-ended livestreams don't tend to do well in tech, even though they can often do so for other genres like gaming.

It's always good to look back on projects like this and question at the end if it's worth it—both in terms of the monetary reward, and the intangibles.

Is it worth it (otherwise)?

So here's the million-dollar-question: would I have rather built a pre-recorded course for one of the traditional learning platforms like Pluralsight or Udemy, or done this streaming series?

Well, this year my goal has been to break out and do my own thing. Being put into a schedule and content framework controlled by others is not that.

So I think it was worth it from the 'I accomplished this' perspective, but slightly less worth it from the 'the immediate benefit is worth the investment' perspective.


Publishing a new book using the series' content

I decided that I could extend the shelf-life of the content I spent so many hours building up (I mean, who else builds full CI coverage for examples in video content?). So I turned the series into a book with the same name:

Kubernetes 101 Book Cover

Like my two current self-published books (Ansible for DevOps and Ansible for Kubernetes), I'm a firm believer in self-publishing so I can write—and keep updated—the best technical content.

So I'm translating all the content I made for the video series into written form, in the book Kubernetes 101, which I've already started publishing on LeanPub (pre-completion). If you get the book from LeanPub, you get DRM-free updates to the book, free forever.

Once I finish writing the first 'final' version, I'll also be publishing on Amazon and iTunes, along with a paperback version through Amazon's Kindle Direct Publishing.

I've blogged quite a bit about self-publishing in the past, and I'd encourage you to consider it. Most of the time, especially for first-time tech authors, the terms of a publishing deal are tilted extraordinarily heavy in the publisher's favor. If you have a breakout success, wouldn't it be nice to see some of the profits from it?

And if not, it's better to get 70% of a pittance than almost nothing.


It sounds like a nice book but I feel a little betrayed, can you consider finishing Ansible for Kubernetes before investing your time on a new book, I have been holding my self from reading the 60% version waiting to read a complete book.

Now that I'm finished with the Kubernetes 101 series, I should finally have some time to finish up the Ansible for Kubernetes book—it's been on pause for a few months with the new baby and the conclusion of the live streams.