-
Language:
English
-
Language:
English
Release Notes and Known Issues
Highlighted features and identified problems in CodeReady Containers 1.2
Kevin Owen
kowen@redhat.comdevtools-docs@redhat.com
Abstract
Part I. Release notes
This section documents the most important features and bug fixes in the CodeReady Containers 1.2 product.
Chapter 1. Component versions
CodeReady Containers 1.2 is shipped with the following versions of the main components:
Table 1.1. CodeReady Containers, Component versions
| Component | Version |
|---|---|
| OpenShift Container Platform | 4.2.8 |
|
OpenShift client binary ( | v4.4.0 |
Chapter 2. Changes and improvements
This section highlights some of the notable changes introduced in CodeReady Containers 1.2.
2.1. New features
CodeReady Containers brings a minimal, preconfigured OpenShift Container Platform 4.2 cluster to your local laptop or desktop computer for development and testing purposes. CodeReady Containers is delivered as a Red Hat Enterprise Linux virtual machine that supports native hypervisors for Linux, macOS, and Microsoft Windows 10.
- CodeReady Containers is designed for local development and testing on an OpenShift 4 cluster. To run an OpenShift 3 cluster locally, see Red Hat Container Development Kit.
- Certificates are now automatically recovered once they have expired. The certificate recovery process adds approximately three minutes to the virtual machine start time.
2.1.1. Technology Previews
Support for these features falls under the Technology Preview Features Support Scope.
-
On Windows 10, an alternative network for Hyper-V can now be used. Create a virtual switch named
crcto connect to an alternative network segment or network adapter (provided that there is a DHCP server on this network).
2.1.2. Usability improvements
- macOS now gets a fixed IP address. As a result, network restarts are less frequent.
2.2. Notable changes
- Support for the VirtualBox hypervisor has been deprecated and will be removed in the next release.
Part II. Known issues
This section describes issues that users of CodeReady Containers 1.2 may encounter, as well as possible workarounds for these issues.
Chapter 3. General issues
Issues affecting all supported platforms.
3.1. Embedded certificates expire after 30 days
Each released crc binary includes an embedded system bundle that expires 30 days after the release due to certificates embedded in the OpenShift cluster.
Certificate recovery is automatic, but will add approximately three minutes to the start time of the CodeReady Containers virtual machine.
3.2. Metrics are disabled by default
To ensure CodeReady Containers can run on a typical laptop, some resource-heavy services are disabled by default. One of these services is Prometheus and all of the related monitoring, alerting, and telemetry functionality.
Enabling these features will require more resources than the CodeReady Containers virtual machine uses by default.
Chapter 4. Issues on Microsoft Windows
This section describes CodeReady Containers issues that affect users on a Microsoft Windows host.
4.1. Unexpected behavior when run outside of %WINDRIVE%
The Hyper-V driver will fail when the crc binary is executed from a network drive. The crc binary must be placed in a location on %WINDRIVE%. %WINDRIVE% is normally set to C:\.
Additional resources
- See the Red Hat CodeReady Containers Getting Started Guide for an overview of CodeReady Containers features and an introduction to the use of OpenShift Container Platform.
-
Report issues with CodeReady Containers or request new features using the OpenShift Container Platform product with the
crccomponent on Red Hat BugZilla.