-
Language:
English
-
Language:
English
Release Notes and Known Issues
Highlighted features and identified problems in CodeReady Containers 1.0
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.0 product.
Chapter 1. Component versions
CodeReady Containers 1.0 is shipped with the following versions of the main components:
Table 1.1. CodeReady Containers, Component versions
| Component | Version |
|---|---|
| OpenShift Container Platform | 4.2.0 |
|
OpenShift client binary ( | v4.3.0 |
Chapter 2. Changes and improvements
This section highlights some of the notable changes introduced in CodeReady Containers 1.0.
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.
Start a local OpenShift 4 cluster with two commands:
-
The
crc setupcommand performs operations to set up the prerequisites for your host environment. -
Once set up is complete, the
crc startcommand handles interaction with the hypervisor and deploys the OpenShift cluster.
-
The
-
CodeReady Containers includes a cached
ocbinary for interacting with the OpenShift cluster. Follow the instructions printed by thecrc oc-envcommand to add the cachedocbinary to yourPATH.
Part II. Known issues
This section describes issues that users of CodeReady Containers 1.0 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. Using an older crc binary or system bundle will result in an expired certificates error.
To resolve expired certificate errors:
-
Download the latest CodeReady Containers release and place the
crcbinary in your$PATH. Remove the cluster with certificate errors using the
crc deletecommand:$ crc delete
NoteThe
crc deletecommand will result in the loss of data stored in the CodeReady Containers virtual machine.Set up the new release:
$ crc setup
Start the new cluster:
$ crc start
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.
To start the monitoring, alerting, and telemetry services:
$ oc scale --replicas=1 statefulset --all -n openshift-monitoring; oc scale --replicas=1 deployment --all -n openshift-monitoring
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.