What's the worst part about provisioning bare metal machines? And why would you opt to deploy Red Hat OpenShift on a bare metal server over a virtual machine anyway? In this episode we take an in-depth look at bare metal provisioning with OpenShift Container Platform.

More specifically, Rhys Oxenham and Ben Schmaus, both from the Customer and Field Enablement team, along with Ramon Acedo, OpenShift product manager, join us to examine and demo bare metal with the installer-provisioned infrastructure (IPI) method. This includes a look at the prerequisites, and setting up the environment for success. 

As always, please see the list below for additional links to specific topics, questions, and supporting materials for the episode!

If you’re interested in more streaming content, please subscribe to the Red Hat livestreaming calendar to see the upcoming episode topics and to receive any schedule changes. If you have questions or topic suggestions for the Ask an OpenShift Admin Office Hour, please contact us via Discord, Twitter, or come join us live, Wednesdays at 11am EDT / 1500 UTC, on YouTube and Twitch.

Episode 45 recorded stream:


Use this link to jump directly to where we start talking about today’s topic. 

This week’s top of mind topics:

  • VMworld 2021 happened the week of October 5-7, you can find all of the OpenShift sessions at this link, including one which I co-presented - MCL3142S.
  • If you missed it, the OpenShift product management team delivered the “What’s New” session for OpenShift 4.9 on October 7th. This nearly two hour session covers a huge number of the changes and additions to OpenShift in the soon-to-be-released version 4.9.
  • By the time you’re reading this KubeCon 2021 North America will have concluded. If you’re interested in Red Hat’s presence - sessions, booth, pre-event events, and more - please visit the landing page here.
  • Our last topic for this week is the poison pill Operator. The docs were recently added for this Operator, so it’s relatively unknown at this point. The short version is that this Operator provides a method to quickly identify when a node has failed and reschedule workload which was hosted on it.

Questions answered and topics discussed during the stream: