Scott's Weblog The weblog of an IT pro specializing in cloud computing, open source, networking, and virtualization

List of Kubernetes Folks on Twitter

Earlier this morning, I asked on Twitter about good individuals to follow on Twitter for Kubernetes information. I received quite a few good responses (thank you!), and I though it might be useful to share the list of the folks that were recommended across all those responses.

The list I’ve compiled is clearly incomplete! If you think someone should be added to this list, feel free to hit me up on Twitter and let me know. Alternately, feel free to submit a pull request (PR) that adds them to this list. I’m not going to “vet” the list, so I’ll add any and all recommendations (unless they are clearly not related to Kubernetes, such as a news anchorman someone recommended to me—not sure about that one!).

Without further ado, here is the list I compiled from the responses to my tweet, in no particular order (I’ve included full name and employer, where that information is available):

  • Kelsey Hightower (Google) - @kelseyhightower
  • Jessie Frazelle (Microsoft) - @jessfraz
  • Alex Ellis (VMware) - @alexellisuk
  • Michael Hausenblas (Red Hat) - @mhausenblas
  • Ahmet Alp Balkan (Google) - @ahmetb
  • AdNaN Abdulhussein (Bitnami) - @prydonius
  • Tim Hockin (Google) - @thockin
  • Joe Beda (Heptio) - @jbeda
  • Joseph Jacks (Unknown) - @asynchio
  • Stefan Schimanski (Red Hat) - @the_sttts
  • Brandon Philips (CoreOS/Red Hat) - @brandonphilips
  • Ray Tsang (Google) - @saturnism
  • Ilya Dmitrichenko (Weaveworks) - @errordeveloper
  • Brendan Burns (Microsoft) - @brendanburns
  • Kris Nova (Heptio) - @krisnova
  • Paris (Google) - @parisinbmore
  • Amy Chen (Heptio) - @theamycode
  • Ria Bhatia (Microsoft) - @rbitia
  • Celina (Uber) - @shaleenaa
  • Chen Goldberg (Google) - @goldbergchen
  • Aparna Sinha (Google) - @apbhatnagar
  • Michelle Noorali (Microsoft) - @michellenoorali
  • Liz Rice (AquaSec) - @lizrice
  • Laura Frank (Codeship) - @rhein_wein
  • Ara Pulido (Bitnami) - @arapulido
  • Rita Zhang (Microsoft) - @ritazzhang
  • Angie Maguire (Unknown) - @lalamaguire
  • Nikhita Raghunath (Red Hat) - @thenikhita
  • Rob Hirschfeld (RackN) - @zehicle
  • Brian Gracely (Red Hat) - @bgracely
  • Steve Watt (Red Hat) - @wattsteve
  • Diane Mueller (Red Hat) - @pythondj
  • Clayton Coleman (Red Hat) - @smarterclayton
  • Craig McLuckie (Heptio) - @cmcluck
  • Benjamin Hindman (Mesosphere) - @benh
  • Armon Dadgar (HashiCorp) - @armon
  • Stu Miniman (Wikibon) - @stu
  • Adrian Cockcroft (AWS) - @adrianco
  • Edaena Salinas (Microsoft) - @edaenas
  • Matt Klein (Lyft) - @mattklein123
  • Ben Sigelman (LightStep) - @el_bhs
  • Dan Kohn (CNCF) - @dankohn1
  • Nigel Poulton (Pluralsight) - @nigelpoulton
  • Justin Garrison (Disney) - @rothgar
  • Mark Mandel (Google) - @neurotic
  • Michael Gasch (VMware) - @embano1
  • Sebastien Goasguen (Bitnami) - @sebgoa
  • Victor Farcic (CloudBees) - @vfarcic
  • Ben Hall (Katacoda) - @ben_hall

Some folks were explicitly called out as “influencers,” but I did not include that designation in the list above. It seems like a slippery slope to determine who is an influencer and who is not, so I’d rather just avoid any potential issues.

Here’s hoping others find this list useful!

Review: Lenovo ThinkPad X1 Carbon

As part of the transition into my new role at Heptio (see here for more information), I had to select a new corporate laptop. Given that my last attempt at running Linux full-time was thwarted due primarily to work-specific collaboration issues that would no longer apply (see here), and given that other members of my team (the Field Engineering team) are also running Linux full-time, I thought I’d give it another go. Accordingly, I’ve started working on a Lenovo ThinkPad X1 Carbon (5th generation). Here are my thoughts on this laptop.

This is now my second non-Apple laptop in the last year. My previous non-Apple laptop, a Dell Latitude E7370, was a pretty decent laptop (see my review). As good as the E7370 was, though, the X1 Carbon is better.

The X1 Carbon features a dual-core i7 7500U CPU, which (subjectively, anyway) outperforms the mobile CPU in the E7370. This makes the X1 Carbon feel quite snappy and responsive. CPU performance was an issue for me with the Dell—it didn’t take much to tax that mobile CPU. I haven’t seen that issue so far with the X1 Carbon. Coupled with 16GB of RAM, the X1 Carbon is no slouch. My particular model only came with a 256GB NVMe SSD (the E7370 had a 512GB NVMe SSD), but given that I won’t be storing tons of media files or dozens of VMs I don’t anticipate that the smaller disk will be an issue.

Like the E7370, the X1 Carbon also leverages Intel HD graphics. This is one area where the Dell may have had an edge on the X1 Carbon; the Dell offered a 3200x1800 touchscreen, whereas the X1 Carbon—my particular model—supports 1920x1080, and no touchscreen support. To be fair, I ended up running the Dell at a lower resolution to work around issues pertaining to scaling with external monitors, so the lower resolution of the X1 Carbon isn’t really a big deal. I also didn’t use the touchscreen functionality, so I don’t miss it either. Screen quality and brightness are really good, in my opinion.

Like many other laptops, the ThinkPad also uses an Intel wireless card with support for all the major 802.11 standards. Wireless performance thus far has been pretty respectable; I haven’t run into any issues or problems.

Battery life has (so far) been very good. I’m impressed. I haven’t even done any tuning yet, and the battery life easily surpasses the E7370 (which was fairly decent).

I do feel that I need to call out the keyboard on the X1 Carbon, which is nothing short of fantastic. It is handily far better than the keyboards on the latest MacBook Pros (which have had no end of problems). It’s probably the best laptop keyboard I’ve used in quite a while.

The quality of the laptop is good. It feels strong and sturdy but is still light and thin, making it easy to carry while traveling (an important aspect for me). I didn’t know quite what to expect since this was my first ThinkPad (hard to believe, right?).

Last, but not least, how is the X1 Carbon with regards to Linux support? With the exception of the fingerprint scanner (which is a known issue), everything works out of the box with Fedora 27. Keyboard function keys work without any fiddling or extra configuration required, suspend (by closing the lid) and resume work without any issues, and both the trackpoint and the trackpad work as expected. I’d seen some reports that one or the other needed to be disabled, but both have been working for me without any issues.

Overall, I’m pretty happy with the ThinkPad X1 Carbon, and would recommend it to anyone looking for a lightweight but powerful laptop on which to run Linux.

The Future is Containerized

Last week I announced my departure from VMware, and my intention to step away from VMware’s products and platforms to focus on a new technology area moving forward. Today marks the “official” start of a journey that’s been building for a couple years, a journey that will take me into a future that’s containerized. That journey starts in Seattle, Washington.

Why Seattle, Washington? Because that’s where Heptio is based, and because today I am joining Heptio as a senior member of the field engineering team to help drive the adoption of Kubernetes across the industry. Only a couple of folks guessed that I was headed to Heptio. If you were one of those folks, you guessed correctly!

Two questions are probably rolling around in your head right now:

  1. Why Kubernetes?
  2. Why Heptio?

Good questions!

It’s clear to me that containers will have a significant impact on how we as IT professionals will develop, deploy, upgrade, and manage applications. It’s also clear to me that when it comes to orchestrating containers, Kubernetes is the clear leader. So, if I accept that containers are going to be a significant part of IT moving forward, then it logically follows that Kubernetes is the technology area where I should focus. There’s the answer to your first question.

As to the second question: if I’m going to focus on Kubernetes, then I want (need?) to work on a team that is passionate about Kubernetes, and that team should have deep expertise in Kubernetes. Because Kubernetes is an open source project, it should be a team that embraces open source, is deeply involved in Kubernetes development, and is committed to the future of Kubernetes. Which team meets all those criteria? In my opinion, Heptio. Founded by two ex-Google employees who helped launch Kubernetes while they were at Google (Craig McLuckie and Joe Beda), the company is actively involved in open source, actively involved in Kubernetes development, actively committed to the future of Kubernetes, and is building a world-class team. I’m honored and thrilled to be part of this team! I’m excited to be able to dive deep into “all things Kubernetes,” and equally excited to get to help design and deploy solutions to customer problems using Kubernetes.

With my destination and new technology focus revealed, my list of 2018 projects/goals probably makes a lot more sense. You can probably also guess that the content here on the site will shift (even more) toward Kubernetes, infrastructure as code, public cloud providers, DevOps, and even some programming/development (I’m looking forward to leveraging some of the development expertise of my peers to “level up” my own programming skills, particularly in Go [Golang]). If you’re active on Slack, then you’ll probably start seeing me around the Kubernetes Slack team more frequently. Of course, you’re always welcome to hit me up on Twitter.

I mentioned last week that I’d miss the VMware community, but I am encouraged by the opportunity to build relationships in the Kubernetes community. There are many great folks within the Kubernetes community (more than a few of them work at Heptio!), and I’m really looking forward to making new friends, building new relationships, and giving back to the community in whatever form I am able.

Lots of hard work lies ahead of me—reshaping oneself and one’s skill set is never an easy thing to do—but I’m genuinely looking forward to this adventure. I’m going to learn a lot, I’m going to grow a lot, and I’m going to do my best to help others along their paths as well. Let’s do this!

Technology Short Take 97

Welcome to Technology Short Take 97! This Tech Short Take marks the end of an era (sort of); it’s the last Tech Short Take published while I’m a VMware employee (today is my last day; see here for more details). But enough about me—let’s talk some tech! This Short Take may be a bit longer than some, so buckle up.



  • Thomas Maurer has a “first impressions” post on the Microsoft Surface Book 2. (I must admit I’ve been considering adding a Microsoft device to my collection.)


Cloud Computing/Cloud Management

  • William Lam has a series of posts on VMware Pivotal Container Service (PKS), which at the time of this writing was up to 4 posts in the series. William provides an overview in part 1, discusses client tools in part 2, reviews NSX-T integration in part 3, and actually kicks off the PKS installation with Ops Manager and BOSH in part 4.
  • Gerald Venzi shows how to use Vagrant and VirtualBox to deploy a local Kubernetes cluster, using some Kubernetes support recently added to an Oracle GitHub repository of Vagrant boxes.
  • Thorsten Hans walks through upgrading a Kubernetes cluster on AKS using the Azure CLI. I myself have done this a couple of times—it’s really straightforward.
  • Trying to decide between GKE, AKS, and EKS? Tirumarai Selvan has a comparison.
  • Richard Li discusses strategies for ingress in Kubernetes and the tradeoffs associated with each approach.

Operating Systems/Applications

  • Eben Freeman shows how to integrate Istio, Envoy, and Honeycomb for detailed application statistics.
  • Antonio Murdaca outlines how to use kubeadm to bootstrap a Kubernetes cluster with CRI-O (instead of Docker). I haven’t tried this myself yet—I’m waiting for CRI-O to get a bit more mature so that I don’t have to compile it from source (although this is an older article, so we might be there by now).
  • If I ever get my hands on a Windows 10 box (I’m seriously considering adding a Windows 10 box to my home office setup), I’m going to try this process. Hmmm…maybe I could install Windows 10 on my quad-proc Mac Pro, then run macOS virtualized on it…that might be something to try one day (as if I’ll ever have time for that!).
  • Ansible 2.5 was recently released; check out this post detailing some of the new features and functionality.
  • Dusty Mabe talks about using BTRFS snapshots to snapshot and rollback entire installations of Fedora, and (rightfully) mentions Atomic Workstation as a (probably) better alternative. Still, the idea is pretty cool.
  • Flatcar Linux is a “friendly fork” of Container Linux (of CoreOS).
  • Windows Server 2019 is now in preview (see this blog post), and will include Kubernetes support. Also see this VentureBeat article.
  • Nick Joyce walks through a few tips to build more minimal Docker containers for Python applications.
  • JJ Asghar provides some direct steps to getting PowerCLI 10+ working on Ubuntu Linux.


No links for you this time, but I’ll stay alert for something to include next time. If you have links you’d like to see included in the next Technology Short Take, send them my way!


Nothing this time around—it seems like all the “cool kids” are talking about cloud, containers, and Kubernetes these days! Don’t worry, though, I’ll keep my eyes peeled for some content to include here next time around.

Career/Soft Skills

  • Finding yourself procrastinating more than usual recently? There can be a lot of different reasons; this post by Leo Babauta explores some reasons and some antidotes for procrastination.
  • Guess I should’ve read this post by Greg Ferro on why you will never make serious money working for a startup before I took a job at a startup. (Oops! That’s a hint toward Monday’s announcement!)

It’s time to wrap up. Have a great weekend, everyone!

Time to Evolve

I first started getting into VMware around 2003, possibly earlier (I can’t recall exactly when it was). I remember thinking that VMware’s impact on the industry was going to be significant, and I wanted to be part of this industry change. I was right—virtualization like what VMware offers has fundamentally changed the industry. However, just as technology evolves, technology careers must evolve as well. Specifically, my technology career must change and grow. It’s time to evolve.

This need to evolve has been building for a couple years. You’ve probably observed that the amount of VMware-centric content produced here on the site has slowly been replaced by topics like Linux, Docker, Vagrant, Terraform, AWS, Azure, and others. These topics represent where I think my next period of growth and change resides, and after a couple years of slow growth in these areas it’s now time to “put the pedal to the metal” and accelerate things.

As of this coming Friday, March 30, 2018, I will be leaving VMware after a little over 5 years with the company. My time with VMware (as an employee) has been an amazing adventure. I’m thankful to Brad Hedlund for his Twitter DM asking me, “Would you be interested in talking to Martin Casado?”, and I’m thankful to Martin for giving me an opportunity to be part of the network virtualization vanguard at VMware. I’ve met some incredible people, learned many things, worked with amazing teams, and contributed to important projects.

Not only am I leaving VMware as an employee, but I’m also leaving VMware as a focus area. After about 15 years of being focused almost exclusively on VMware products and platforms, I’m stepping away from VMware to focus and concentrate on a new technology direction.

I’ll talk more about my new focus next week when I announce where I’m headed following my departure from VMware. Naturally, this decision to focus on a new technology direction means some changes. Often, in order to say “yes,” one must also say “no.” In this particular case, in order to say “yes” to focusing on a new technology direction, I must say “no” to being well-versed in VMware’s products and platforms. Similarly, in order to say “yes” to being an engaged member of a new technical community, I must say “no” to being closely involved in the VMware community.

It is, perhaps, the VMware community that I will miss the most; it’s been part of my professional life for more than a few years. So, what does this mean? Moving forward, it won’t make sense for me to be involved in user group events, and I probably won’t continue to be a vExpert (2018 is already in the bag, marking a ten-year run, but 2019 probably won’t happen—and that’s OK). I don’t foresee maintaining my VCDX. These are fully expected consequences of switching my focus away from VMware’s platforms. Although I expect I will always have friends within the community, it simply doesn’t make sense to be as active and involved as I have been in the past.

While I am saddened by the thought of not being so involved in the VMware community, I am encouraged by the opportunity to build relationships in a new community. I’m hopeful that I can make a positive impact in some small way. That’s my goal, anyway.

It probably goes without saying, but I’ll continue to publish content here, although the content will (naturally) shift even further away from VMware-related topics. What can you expect to see? My list of 2018 projects/goals provides a few clues. I’ll continue to remain active on Twitter, and there are a few different Slack communities where you’re likely to spot me as well.

Change is an integral part of life, and it’s an integral part of every person’s career (or should be, anyway!). The time has come to embrace this change and make the most of the opportunity. It’s time to evolve. Exciting times are ahead!

Recent Posts

Interop ITX, Dell Technologies World, and Spousetivities

Spousetivities will be present at two additional events this year—in fact, these events are only about 6 weeks away! Both Dell Technologies World and Interop ITX are in Las Vegas the last week of April (both starting April 30), and Spousetivities is running events for both conferences.


Technology Short Take 96

Welcome to Technology Short Take 96! Ahead, lying in wait, is a unique collection of links, articles, and thoughts about various data center technologies. Browse if you dare…OK, so I’m being a bit melodramatic. It’s still some good stuff here!


Recent Changes in my "Learning Tools" Repository

A couple years ago, I created a “learning-tools” repository on GitHub with the goal of creating environments/tools that would help others learn new technologies. At first, the contents of the repository were almost exclusively leveraging Vagrant, but over time I’ve extended the environments to also leverage Ansible and to use tools such as Terraform. Over the past month or so, I’ve made a few additional (albeit relatively minor) updates that I also wanted to share.


Looking Ahead: My 2018 Projects

For the last six years or so, I’ve been publishing a list of projects/goals for the upcoming year (followed by a year-end review of how I did with those projects/goals). For example, here are my goals for 2017, and here’s my year-end review of my progress in 2017. In this post, I’m going to share with you my list of projects/goals for 2018.


Technology Short Take 95

Welcome to Technology Short Take 95! This Short Take was a bit more challenging than normal to compile, given that I spent the week leading up to its publication visiting customers in Europe. (My travel schedule in Europe is also why it didn’t get published until Saturday instead of the typical Friday.) Nevertheless, I have persevered in order to deliver you this list of links and articles. I hope it proves useful!


Some Tools to Help Learn Kubernetes

Kubernetes is emerging as the clear leader in the container orchestration space. This makes it an important technology to know and understand. However, like other distributed systems, learning something like Kubernetes can be challenging due to the effort involved in getting Kubernetes up and running. It’s not about learning to set up Kubernetes (although that comes in time); at first, it’s about understanding what Kubernetes does and how to use Kubernetes. In this post, I’ll share some tools to help learn what Kubernetes does and how to use Kubernetes.


Technology Short Take 94

Welcome to Technology Short Take 94! Ready for another round of links, articles, and thoughts on data center technologies? (Who knows, maybe I’ll throw a rant or two in there.) OK, enough rambling…here’s the good stuff!


Running OVS on Fedora Atomic Host

In this post, I’d like to share the results of some testing I’ve been doing to run Open vSwitch (OVS) in containers on a container-optimized Linux distribution such as Atomic Host (Fedora Atomic Host, specifically). I’m still relatively early in my exploration of this topic, but I felt like sharing what I’ve found so far might be helpful to others, and might help spark conversations within the relevant communities about how this experience might be improved.


Using Docker Machine with Azure

I’ve written about using Docker Machine with a number of different providers, such as with AWS, with OpenStack, and even with a local KVM/Libvirt daemon. In this post, I’ll expand that series to show using Docker Machine with Azure. (This is a follow-up to my earlier post on experimenting with Azure.)


An Update on Using Docker Machine with Vagrant

As part of a project on which I’m working, I’ve been spending some time working with Docker Machine and Vagrant over the last few days. You may recall that I first wrote about using these two tools together back in August 2015. As a result of spending some additional time with these tools—which I chose because I felt like they streamlined some work around this project—I’ve uncovered some additional information that I wanted to share with readers.


Technology Short Take 93

Welcome to Technology Short Take 93! Today I have another collection of data center technology links, articles, thoughts, and rants. Here’s hoping you find something useful!


Experimenting with Azure

I’ve been experimenting with Microsoft Azure recently, and I thought it might be useful to share a quick post on using some of my favorite tools with Azure. I’ve found it useful to try to leverage existing tools whenever I can, and so as I’ve been experimenting with Azure I’ve been leveraging familiar tools like Docker Machine and Vagrant.


Issue with VMware-Formatted Cumulus VX Vagrant Box

I recently had a need to revisit the use of Cumulus VX (the Cumulus Networks virtual appliance running Cumulus Linux) in a Vagrant environment, and I wanted to be sure to test what I was doing on multiple virtualization platforms. Via Vagrant Cloud, Cumulus distributes VirtualBox and Libvirt versions of Cumulus VX, and there is a slightly older version that also provides a VMware-formatted box. Unfortunately, there’s a simple error in the VMware-formatted box that prevents it from working. Here’s the fix.


Technology Short Take 92

Welcome to Technology Short Take 92, the first Technology Short Take of 2018. This one was supposed to be the last Tech Short Take of 2017, but I didn’t get it published in time (I decided to spend time with my family instead—some things are just more important). In any case, hopefully the delay of one additional week hasn’t caused any undue stress—let’s jump right in!


Looking Back: 2017 Project Report Card

As has become my custom for the past several years, I wanted to take a look at how well I fared on my 2017 project list. Normally I’d publish this before the end of 2017, but during this past holiday season I decided to more fully “unplug” and focus on the truly important things in life (like my family). So, here’s a look back at my 2017 projects and a report card on my progress (or lack thereof, in some cases).


Older Posts

Find more posts by browsing the post categories, content tags, or site archives pages. Thanks for visiting!