Release Notes and Known Issues
Highlighted features and identified problems in Red Hat OpenShift Local 2.22
Fabrice Flore-Thebault
ffloreth@redhat.comdevtools-docs@redhat.com
Abstract
Making open source more inclusive
Red Hat is committed to replacing problematic language in our code, documentation, and web properties. We are beginning with these four terms: master, slave, blacklist, and whitelist. Because of the enormity of this endeavor, these changes will be implemented gradually over several upcoming releases. For more details, see our CTO Chris Wright’s message.
Chapter 1. Release notes
These are the most important features and bug fixes in the Red Hat OpenShift Local 2.22 product.
1.1. Component versions
Red Hat OpenShift Local 2.22 has the following versions of the main components:
Table 1.1. Red Hat OpenShift Local, Component versions
| Component | Version |
|---|---|
| OpenShift Container Platform | 4.13.3 |
|
OpenShift client binary ( | v4.13.3 |
| Podman binary | 4.4.4 |
1.2. Minimum system requirements
Red Hat OpenShift Local has the following minimum hardware and operating system requirements.
1.2.1. Hardware requirements
Red Hat OpenShift Local is supported on these architectures:
Table 1.2. Preset and architecture compatibility
| Preset | AMD64 | Intel 64 | M1 |
|---|---|---|---|
| OpenShift Container Platform | yes | yes | yes |
| MicroShift | yes | yes | yes |
| Podman container runtime | yes | yes | yes |
Red Hat OpenShift Local does not support nested virtualization.
Depending on the desired container runtime, Red Hat OpenShift Local requires the following system resources:
1.2.1.1. For OpenShift Container Platform
- 4 physical CPU cores
- 9 GB of free memory
- 35 GB of storage space
1.2.1.2. For MicroShift
- 2 physical CPU cores
- 4 GB of free memory
- 35 GB of storage space
The OpenShift Container Platform and MicroShift presets require these minimum resources to run in the Red Hat OpenShift Local instance. Some workloads might require more resources. To assign more resources to the Red Hat OpenShift Local instance, see Configuring the instance.
1.2.1.3. For the Podman container runtime
- 2 physical CPU cores
- 2 GB of free memory
- 35 GB of storage space
1.2.2. Operating system requirements
Red Hat OpenShift Local requires the following minimum version of a supported operating system:
1.2.2.1. Requirements on Microsoft Windows
- On Microsoft Windows, Red Hat OpenShift Local requires the Windows 10 Fall Creators Update (version 1709) or later. Red Hat OpenShift Local does not work on earlier versions of Microsoft Windows. Microsoft Windows 10 Home Edition is not supported.
1.2.2.2. Requirements on macOS
- On macOS, Red Hat OpenShift Local requires macOS 11 Big Sur or later. Red Hat OpenShift Local does not work on earlier versions of macOS.
1.2.2.3. Requirements on Linux
- On Linux, Red Hat OpenShift Local is supported only on the latest two Red Hat Enterprise Linux/CentOS 8 and 9 minor releases and on the latest two stable Fedora releases.
- When using Red Hat Enterprise Linux, the machine running Red Hat OpenShift Local must be registered with the Red Hat Customer Portal.
- Ubuntu 18.04 LTS or later and Debian 10 or later are not supported and might require manual set up of the host machine.
- See Required software packages to install the required packages for your Linux distribution.
1.3. Changes and improvements
These are some notable changes introduced in Red Hat OpenShift Local 2.22.
1.4. Notable enhancements
- You can use Red Hat OpenShift Local for development and testing purposes.
Red Hat OpenShift Local installs on your computer one of these presets:
openshift- A minimal, preconfigured OpenShift Container Platform 4.13 cluster.
microshift- MicroShift.
podman- Podman container runtime.
The preset runs in a Red Hat Enterprise Linux virtual machine, on the native hypervisor, on these platforms:
- Linux
- macOS
- Microsoft Windows 10
1.5. Technology Preview
Support for these features falls under the Technology Preview Features Support Scope.
-
Red Hat OpenShift Local 2.22 includes the ability to create a custom bundle based on the currently running cluster with the
crc bundle generatecommand. This command, its parameters, and behavior might change in incompatible ways in future releases.
1.6. Notable changes
-
Red Hat OpenShift Local 2.22 provides OpenShift Container Platform 4.13.3 in the embedded OpenShift preset (
openshift). -
Red Hat OpenShift Local 2.22 provides Podman 4.4.4 in the embedded Podman container engine preset (
podman). -
Red Hat OpenShift Local 2.22 provides MicroShift 4.13.3 in the embedded MicroShift preset (
microshift).
1.6.1. crc config get returns default values when the property is not set
Previously, crc config get returned an error code when the setting had a default value. With this update, it returns the default value.
Additional resources
1.6.2. Fixed downloading error during setup
Previously, setup was failing with the error: unable to get verified hash for default bundle. This update fixes the bundle hash downloading error in crc setup.
Additional resources
1.6.3. Resizing disks for the MicroShift preset
Previously, it was not possible to resize MicroShift preset disks. This update adds disk-resize functionality for the MicroShift preset.
Additional resources
1.6.4. Fixed DNS lookup from within containers
Previously, DNS messages from Red Hat OpenShift Local DNS service could exceed 512B, and some clients might fail to process the message. With this update, DNS messages are compressed, and container can sucessfully process DNS messages.
Additional resources
Chapter 2. Known issues
Issues that users of Red Hat OpenShift Local 2.22 might have, as well as possible workarounds for these issues.
2.1. General issues
Issues affecting all supported platforms.
2.1.1. Proxy settings are improperly applied to the Podman preset
Proxy settings configured by using the crc config set command are not used by the podman-remote binary embedded in Red Hat OpenShift Local when the Podman preset is in use.
2.1.2. Red Hat OpenShift Local disables metrics by default
To ensure Red Hat OpenShift Local can run on a typical notebook, Red Hat OpenShift Local disables some resource-heavy services, such as Prometheus and all the related monitoring, alerting, and telemetry functions. You can enable these features.
Procedure
- See Configuring the virtual machine to assign more resources
- See Starting Monitoring, Alerting, and Telemetry
You cannot disable Monitoring after enabling these features.
Workaround
To disable monitoring again:
Delete the virtual machine:
$ crc delete
Create a virtual machine:
$ crc start
2.1.3. Enabling many Operators requires more memory than the default
The crc start command assigns 9 GiB of memory to the Red Hat OpenShift Local virtual machine by default. Enabling many Operators might increase memory requirements.
Workaround
- See Configuring the virtual machine to assign additional memory.
2.1.4. Red Hat OpenShift Local does not work when the first nameserver is IPv6
DNS resolution to the Red Hat OpenShift Local virtual machine might fail if the first nameserver is IPv6.
Workaround
Specify an IPv4
nameserverwhen starting the Red Hat OpenShift Local virtual machine by using the-nflag:$ crc start -n 8.8.8.8
2.1.5. Running crc setup might give you a known error
When you run the crc setup command, you might get the following error:
unable to get verified hash for default bundle: Get "https://developers.redhat.com/content-gateway/file/pub/openshift-v4/clients/crc/bundles/openshift/4.12.13/sha256sum.txt.sig": context deadline exceeded (Client.Timeout exceeded while awaiting headers)
Workaround
-
Try running the
crc setupcommand till the error is resolved.
2.2. Issues on Microsoft Windows
This section describes Red Hat OpenShift Local issues that affect users on a Microsoft Windows host.
2.2.1. Completing the installation after installation with the Microsoft Standard Installer (MSI)
Procedure
- Install Red Hat OpenShift Local with the MSI installer
- Reboot your computer
Run the command in Command Prompt or PowerShell:
$ crc setup
2.2.2. The crc cleanup command might fail with a permission error
Running crc setup followed by crc cleanup without restarting your host computer between commands will cause crc cleanup to report the following error:
Post "http://unix/clean": open \\.\pipe\crc-admin-helper: Access is denied.
Workaround
- Reboot your computer
Run the command:
$ crc cleanup
2.2.3. Unexpected behavior when run outside %WINDRIVE%
The Hyper-V driver will fail when you start the crc binary from a network drive.
Workaround
Move the
crcbinary to a location on%WINDRIVE%.%WINDRIVE%is usually set toC:\.
2.2.4. Red Hat OpenShift Local expects FullLanguage support in PowerShell
Red Hat OpenShift Local supports the ConstrainedLanguage PowerShell mode with exceptions determined by your system administrator.
2.2.5. The crc oc-env command does not work with special characters in %PATH%
On Microsoft Windows, PowerShell and Command Prompt do not use the UTF-8 encoding. Therefore, running the crc oc-env command with special characters present in the %PATH% will not accurately encode UTF-8 characters.
Workaround
-
Move the
crcbinary to a location containing no special characters.
Additional resources
- See the ""Red Hat OpenShift Local"" Getting Started Guide for an overview of Red Hat OpenShift Local features and an introduction to OpenShift Container Platform.
-
Report issues with Red Hat OpenShift Local or request features by using the OpenShift Container Platform product with the
crccomponent on Red Hat Bugzilla.
2.3. Issues on macOS
This section describes Red Hat OpenShift Local issues that affect users on a macOS host.
2.3.1. Hibernation causes VM time to desynchronize
Time in the Red Hat OpenShift Local virtual machine can become desynchronized with the time on your host. This issue occurs if the Red Hat OpenShift Local virtual machine is running when the host machine enters hibernation.
Workaround
Stop the Red Hat OpenShift Local virtual machine:
$ crc stop
Restart the Red Hat OpenShift Local virtual machine:
$ crc start