CRC provides a config option called bundle to configure the location of the bundle. This option is useful when you want to use a bundle that is not the default one or user want to try a bundle which is not part of release but available at the OpenShift mirror location. The bundle option can accept local filesystem paths, container registry URLs, and http/https URLs. This blog post will guide you through the process of using the bundle option using config or setup/start commands.

CRC is a tool that allows you to quickly and easily spin up a local OpenShift cluster. It is a great way to learn about OpenShift/OKD/MicroShift and to test out new features.

If you’re looking to experiment with the upcoming MicroShift release and want to learn how to create the bundle to consume it with CRC, you’re in the right place! This blog post will guide you through the process step by step.

CRC is a tool that allows you to quickly and easily spin up a local OpenShift cluster. It is a great way to learn about OpenShift/OKD/MicroShift and to test out new features.

In this blog post, we will explain to you, how to create an OKD bundle for CRC.

Prerequisites

To create an OKD bundle, you will need the following:

Are you a developer who wants to use OpenShift Kubernetes Engine but doesn’t have a powerful system? Or do you need to deploy to a small form factor or edge computing environment? If so, you’ll be happy to hear about our new MicroShift preset, a lightweight version of OpenShift Kubernetes Engine that’s optimized for resource-limited environments.

The OpenShift preset currently provided by CRC requires 9GB of RAM and 4 CPUs. With the release of CRC 2.16, you can now use the MicroShift preset, which only requires 4GB of RAM and 2 CPUs.

I gave a vfkit presentation today at Container Plumbing Days 2023, the slides can be found here and the talk was recorded.

CRC provides a config option called bundle to configure the location of the bundle, until 2.9 release of CRC the bundle option could only accept local filesystem path which meant users needed to download the bundle in advance before consuming it. The move to a container registry for hosting the okd and podman bundles, introduces another step in the process as bundles are now generated as an OCI container image and the *.crcbundle file needs to be extracted from the image.

It has been long time since CRC with an updated OKD bundle was released. Last release was 1.x and not updated since then. During our 2.x development cycle, we made effort on CRC’s side to decouple the bundles from the release artifacts. It allows us to create the bundle independently of the release and upload it to separate location.

Another change we made during 2.x is to add support for presets and from starting we are supporting podman and openshift preset with openshift as default. With the recently released crc 2.7.1 an okd preset was added and users can now use same crc binary to start a OKD cluster.

With the release of CRC 2.4.1 it was possible to run on Apple’s latest offering of M1-based machines. However, the support was limited to podman preset. Numerous times we received requests if it would be possible to instead offer an OpenShift that would run on these machines. This has changed with the recently released crc 2.7.1. This blog post will describe the challenges we had to overcome when we decided to add that support.

Since its initial release, CRC has been running on macOS as well as on Windows and Linux. However macOS support was limited to Apple machines with an Intel CPUs until recently. With Apple’s ongoing switch to aarch64 M1 CPUs, we’ve been asked numerous times when CRC would get M1 support. This has changed with the recently released crc 2.4.1. This blog post will describe the challenges we had to overcome when we decided to add that support.