Red Hat {product-title} provides developers and IT organizations with a hybrid cloud application platform for deploying both new and existing applications on secure, scalable resources with minimal configuration and management overhead. {product-title} supports a wide selection of programming languages and frameworks, such as Java, JavaScript, Python, Ruby, and PHP.
Built on Red Hat Enterprise Linux and Kubernetes, {product-title} provides a more secure and scalable multi-tenant operating system for today’s enterprise-class applications, while delivering integrated application runtimes and libraries. {product-title} enables organizations to meet security, privacy, compliance, and governance requirements.
Red Hat {product-title} (RHBA-2019:0758) is now available. This release uses Kubernetes 1.13. New features, changes, and known issues that pertain to {product-title} {product-version} are included in this topic.
Red Hat did not publicly release {product-title} 4.0 and, instead, is releasing {product-title} {product-version} directly after version 3.11.
{product-title} {product-version} clusters are available at https://cloud.openshift.com/openshift. The {cloud-redhat-com} application for {product-title} allows you to deploy OpenShift clusters to either on-premise or cloud environments.
{product-title} {product-version} is supported on Red Hat Enterprise Linux 7.6 and later, as well as Red Hat Enterprise Linux CoreOS 4.1.
You must use {op-system-first} for the control plane, or master, machines and can use either {op-system} or Red Hat Enterprise Linux 7.6 for compute, or worker, machines.
|
Important
|
Because only Red Hat Enterprise Linux version 7.6 is supported for compute machines, you must not upgrade the Red Hat Enterprise Linux compute machines to version 8. |
You can install {product-title} {product-version} with installer-provisioned infrastructure on Amazon Web Services (AWS) or user-provided infrastructure on AWS, bare metal, or VMware vSphere hosts. If you use the installer-provisioned infrastructure installation, the cluster provisions and manages all of the cluster infrastructure for you.
{product-title} requires all machines, including the computer that you run the installation process on, to have direct internet access to pull images for platform containers and provide telemetry data to Red Hat. You cannot specify a proxy server for {product-title} {product-version}. This functionality will be reintroduced in a future release.
Red Hat Global Support Services would like to recognize Rushil Sharma, JooHo Lee, and Suresh Gaikwad for their outstanding contributions in evaluating and testing {product-title} 4.1.
Large changes to the underlying architecture and installation process are applied in {product-title} 4.1, and many features from {product-title} 3.x are now deprecated.
| Feature | Justification |
|---|---|
Hawkular |
Replaced by cluster monitoring. |
Cassandra |
Replaced by cluster monitoring. |
Heapster |
Replaced by Prometheus adapter. |
Atomic Host |
Replaced by Red Hat Enterprise Linux CoreOS. |
System containers |
Replaced by Red Hat Enterprise Linux CoreOS. |
|
CRI-O is the default container runtime for {product-title} 4.1 on RHCOS and Red Hat Enterprise Linux. |
|
Operator-based diagnostics. |
|
Replaced by the Image Registry Operator. |
Custom strategy builds using Docker |
If you want to continue using custom builds, you should replace your Docker invocations with Podman or Buildah. The custom build strategy will not be removed, but the functionality changed significantly in {product-title} 4.1. |
Cockpit |
Improved {product-title} 4.1 web console. |
Stand-alone registry installations |
Quay is Red Hat’s enterprise container image registry. |
DNSmasq |
CoreDNS is the default. |
External etcd nodes |
etcd is always on the cluster in {product-title} 4.1. |
CloudForms OpenShift Provider and Podified CloudForms |
Replaced by built-in management tooling. |
Volume Provisioning via installer |
Replaced by dynamic volumes or, if NFS is required, NFS provisioner. |
Blue-green installation method |
Ease of upgrade is a core value of {product-title} 4.1. |
OpenShift Service Broker and Service Catalog |
The Service Catalog and the OpenShift service brokers are being replaced over the course of several future OpenShift 4 releases. Reference the Operator Framework and Operator Lifecycle Manager (OLM) to continue providing your applications to OpenShift 4 clusters. These new technologies provide many benefits around complete management of the lifecycle of your application. |
|
Certificates are managed by Operators internally. |
|
Functions are managed by Operators internally. |
|
|
|
Functions are managed by |
Web console |
The web console from {product-title} 3.11 has been replaced by a new web console in {product-title} 4.1. |
This release adds improvements related to the following components and concepts.
Operators are pieces of software that ease the operational complexity of running another piece of software. They act like an extension of the software vendor’s engineering team, watching over a Kubernetes environment (such as {product-title}) and using its current state to make decisions in real time. Advanced Operators are designed to handle upgrades seamlessly, react to failures automatically, and not take shortcuts, like skipping a software backup process to save time.
This feature is now fully supported in {product-title} 4.1.
The OLM aids cluster administrators in installing, upgrading, and granting access to Operators running on their cluster:
-
Includes a catalog of curated Operators, with the ability to load other Operators into the cluster
-
Handles rolling updates of all Operators to new versions
-
Supports role-based access control (RBAC) for certain teams to use certain Operators
See Understanding the Operator Lifecycle Manager (OLM) for more information.
Red Hat {product-title} 4.1 has an installer-provisioned infrastructure, where the installation program controls all areas of the installation process. Installer-provisioned infrastructure also provides an opinionated best practices deployment of {product-title} 4.1 for AWS instances only. This provides a slimmer default installation, with incremental feature buy-in through OperatorHub.
You can also install with a user-provided infrastructure on AWS, bare metal, or vSphere hosts. If you use the installer-provisioned infrastructure installation, the cluster provisions and manages all of the cluster infrastructure for you.
Upgrading from 3.x to 4.1 is currently not available. You must perform a new installation of {product-title} 4.1.
Easy, over-the-air upgrades for asynchronous z-stream releases of {product-title} 4.1 is available. Cluster administrators can upgrade using the Cluster Settings tab in the web console. See Updating a cluster for more information.
OperatorHub is available to administrators and helps with easy discovery and installation of all optional components and applications. It includes offerings from Red Hat products, Red Hat partners, and the community.
| Feature | New installer | OperatorHub |
|---|---|---|
Console and authentication |
* [x] |
- |
Prometheus cluster monitoring |
* [x] |
- |
Over-the-air updates |
* [x] |
- |
Machine management |
* [x] |
- |
Optional service brokers |
- |
* [x] |
Optional {product-title} components |
- |
* [x] |
Red Hat product Operators |
- |
* [x] |
Red Hat partner Operators |
- |
* [x] |
Community Operators |
- |
* [x] |
See Understanding the OperatorHub for more information.
Updated guidance around Cluster maximums for {product-title} 4.1 is now available.
Use the {product-title} Limit Calculator to estimate cluster limits for your environment.
The Node Tuning Operator is now part of a standard {product-title} installation in version 4.1 and later.
The Node Tuning Operator helps you manage node-level tuning by orchestrating the tuned daemon. The majority of high-performance applications require some level of kernel tuning. The Node Tuning Operator provides a unified management interface to users of node-level sysctls and more flexibility to add custom tuning, which is currently a Technology Preview feature, specified by user needs. The Operator manages the containerized tuned daemon for OpenShift Container Platform as a Kubernetes DaemonSet. It ensures the custom tuning specification is passed to all containerized tuned daemons running in the cluster in the format that the daemons understand. The daemons run on all nodes in the cluster, one per node.
This feature, currently in Technology Preview, enables you to configure horizontal pod autoscaling (HPA) based on the custom metrics API. As part of this Technology Preview, a Prometheus Adapter component can be deployed to provide any app metrics for the custom metrics API.
Limitations:
-
The adapter only connects to a single Prometheus instance (or a set of load-balanced replicas, using Kubernetes services).
-
Manually deploying adapter and configuring it to use Prometheus.
-
Syntax for the Prometheus Adapter configuration could change in the future.
-
The
APIServiceconfiguration to wire Kubernetes' API aggregation to the instance of the custom metrics adapter will be overwritten in future releases, if {product-title} ships an out-of-the-box custom metrics adapter.
An alerting UI is now natively integrated into the {product-title} web console. You can now view cluster-level alerts and alerting rules from a single place, as well as configure silences.
Telemeter collects anonymized cluster-related metrics to proactively help customers with their {product-title} clusters. This helps:
-
Gather crucial health metrics of {product-title} installations.
-
Enable a viable feedback loop of {product-title} upgrades.
-
Gather the cluster’s number of nodes per cluster and their size (CPU cores and RAM).
-
Gather the size of etcd.
-
Gather details about the health condition and status for any OpenShift framework component installed on an OpenShift cluster.
The cluster network is now configured and managed by an Operator. The Operator upgrades and monitors the cluster network.
Multus is a meta plug-in for Kubernetes Container Network Interface (CNI), which enables a user to create multiple network interfaces per pod.
{product-title} 4.1 includes the Technical Preview capability to use specific SR-IOV hardware on {product-title} nodes, which enables the user to attach SR-IOV virtual function (VF) interfaces to Pods in addition to other network interfaces.
{product-title} 4.1 features a redesigned Developer Catalog that brings all of the new Operators and existing broker services together, with new ways to discover, sort, and understand how to best use each type of offering. The Developer Catalog is the entry point for a developer to access all services available to them. It merges all capabilities from Operators, the Service Catalog, brokers, and Source-to-Image (S2I).
{product-title} 4.1 introduces the following notable technical changes.
Source and Docker strategy builds are now performed by buildah instead of the docker daemon.
SecurityContextConstraints now only exist in the security.openshift.io group.
Pods can trust cluster-created certificates, which are only signed for internal
DNS names, by using a CA bundle that is automatically injected into any
configMap annotated with service.beta.openshift.io/inject-cabundle=true. The
CA bundle will be made available as PEM-encoded data under the key
service-ca.crt. This annotation results in wiping out existing content in the
configMap.
Pods that currently consume the service-serving CA bundle from
/var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt should migrate to
obtaining the CA bundle from a configMap annotated with
service.beta.openshift.io/inject-cabundle=true.
The /var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt file is now
deprecated and will be removed in a future release.
The Service Catalog and the OpenShift service brokers are being replaced over the course of several future OpenShift 4 releases. Red Hat will be deprecating the Template Service Broker and OpenShift Ansible Broker once important dependent content is ported to new Operator-driven solutions. Users are encouraged to look at the Operator Framework and Operator Lifecycle Manager (OLM) to continue providing their applications to OpenShift 4 clusters. These new technologies provide many benefits around complete management of the lifecycle of your application.
The Service Catalog is not installed by default in {product-title} 4.1. You must
install it if you plan on using any of the services from the OpenShift Ansible
broker or template service broker. In {product-title} 4.1, the Service Catalog
API server is installed into the openshift-service-catalog-apiserver namespace
and the Service Catalog controller manager is installed into the
openshift-service-catalog-controller-manager namespace. In {product-title}
3.11, both of these components were installed into the kube-service-catalog
namespace.
The Template Service Broker is not installed by default in {product-title} 4.1. Cluster administrators can install the Template Service Broker if users will need access to template applications from the web console.
The OpenShift Ansible Service Broker is not installed by default in {product-title} 4.1.
Deprecated oc adm commands include:
-
oc adm create-master-certs- Create keys and certificates -
oc adm create-key-pair- Create an RSA key pair. -
oc adm create-server-cert- Create a key and server certificate. -
oc adm create-signer-cert- Create a self-signed CA.
The configurability of the imagepolicyadmission plug-in is not present in
{product-title} 4.1. The plug-in runs, but currently only with default
configuration. Configuring it requires using the unsupported overrides
mechanism.
Some features in this release are currently in Technology Preview. These experimental features are not intended for production use. Note the following scope of support on the Red Hat Customer Portal for these features:
In the table below, features marked TP indicate Technology Preview and features marked GA indicate General Availability.
| Feature | OCP 3.11 | OCP 4.1 |
|---|---|---|
Prometheus Cluster Monitoring |
GA |
GA |
Local Storage Persistent Volumes |
TP |
TP |
CRI-O for runtime pods |
GA* [1] |
GA |
|
TP |
TP |
Service Catalog |
GA |
GA |
Template Service Broker |
GA |
GA |
OpenShift Ansible Service Broker |
GA |
GA |
Network Policy |
GA |
GA |
Multus |
- |
GA |
Service Catalog Initial Experience |
GA |
GA |
New Add Project Flow |
GA |
GA |
Search Catalog |
GA |
GA |
Cron Jobs |
GA |
GA |
Kubernetes Deployments |
GA |
GA |
StatefulSets |
GA |
GA |
Explicit Quota |
GA |
GA |
Mount Options |
GA |
GA |
System Containers for CRI-O |
- |
- |
Hawkular Agent |
- |
- |
Pod PreSets |
- |
- |
experimental-qos-reserved |
TP |
TP |
Pod sysctls |
GA |
GA. See Known issues for current limitations. |
Central Audit |
GA |
GA |
Static IPs for External Project Traffic |
GA |
GA |
Template Completion Detection |
GA |
GA |
|
GA |
GA |
Fluentd Mux |
TP |
TP |
Clustered MongoDB Template |
- |
- |
Clustered MySQL Template |
- |
- |
ImageStreams with Kubernetes Resources |
GA |
GA |
Device Manager |
GA |
GA |
Persistent Volume Resize |
GA |
GA |
Huge Pages |
GA |
GA |
CPU Pinning |
GA |
GA |
Admission Webhooks |
TP |
GA |
External provisioner for AWS EFS |
TP |
TP |
Pod Unidler |
TP |
TP |
Node Problem Detector |
TP |
TP |
Ephemeral Storage Limit/Requests |
TP |
TP |
CephFS Provisioner |
TP |
- |
Podman |
TP |
TP |
Sharing Control of the PID Namespace |
TP |
TP |
Manila Provisioner |
TP |
- |
Cluster Administrator console |
GA |
GA |
Cluster Autoscaling (AWS Only) |
GA |
GA |
Container Storage Interface (CSI) |
TP |
TP |
Operator Lifecycle Manager |
TP |
GA |
Red Hat OpenShift Service Mesh |
TP |
GA |
"Fully Automatic" Egress IPs |
GA |
GA |
Pod Priority and Preemption |
GA |
GA |
Multi-stage builds in Dockerfiles |
TP |
GA |
HPA custom metrics adapter based on Prometheus |
TP |
|
Machine health checks |
TP |
|
SR-IOV |
TP |
|
OpenShift Serverless |
TP |
-
Unsafe sysctl cannot be used in {product-title} 4.1. (BZ#1690754)
-
If an instance is removed from the cloud provider (either via a user deletion, or cloud-provider event of some kind), and the machine-object is reconciled again for some reason, the machine-controller might determine the instance no longer exists and attempt to create the instance. This is undocumented behavior and should not be relied upon for workflows. This operation might interfere with current or future components, such as the node-health-checker. (BZ#1712068)
-
Builds which use shell substitution to populate an environment variable may fail. (BZ#1712245)
-
When deleting a machine-object, either directly or by scaling down the owning machine-set, if the associated node has already been deleted somehow (possibly by a cluster administrator), the machine-controller will fail to successfully delete the backing cloud instance, and the machine-object will be stuck in
deletingstatus. (BZ#1713061) -
Querying
JolokiaonJBoss EAPimages fails as the result of empty certificates presented to the client. TheJolokiaSSL client authentication will fail and may require a username and password challenge if enabled. (BZ#1708640) -
The
TokenRequestAPI is not available in {product-title} 4.1. Requesting aServiceAccountTokenVolumeProjectionvolume is not available in {product-title} 4.1. The kubelet will present an error if aServiceAccountTokenVolumeProjectionis used. (BZ#1695196) -
The
es nodeCountin Elasticsearch CRD instances can not be scaled up if deployed with three nodes. Scaling works correctly if deployed with one, two, four, five or six Elasticsearch CRD instances. (BZ#1712955) -
Elasticsearch instances created from OperatorHub deploy with a one CPU limit, even though no limits are specified. (BZ#1710657)
-
After an AWS installation, the
openshiftClustIDtag is not present. (BZ#1685089) -
scc(CRD) resources can not be upgraded by using the
oc patchandoc editcommands. As a result, strategic merges also fail. (BZ#1707679) -
The {product-title} 4.1 registry service utilizes port 5000 instead of port 443. (BZ#1701422)
-
Machineset scaling in AWS environments may fail if the resources requested are unavailable in the chosen Availability Zone. (BZ#1713157)
-
Using
OAuthendpoints after configuring ingress wildcard certificates from custom PKIs result in login errors. (BZ#1712525) -
Source-to-Image (S2I) builds in {product-title} 4.1 may take longer to complete. This is because {product-title} 4.1 does not utilize a shared image cache for building images like in previous versions of {product-title}. (BZ#1685352)
-
The
cloud-credential-operatormay crash on clusters with large numbers of projects or namespaces due to memory limitations. (BZ#1711402) -
The Marketplace can not detect
opsrcafter a cluster upgrade is performed. As a result, thecscpackages are empty and can not downloadpackagemanifests. Marketplace can repair this problem approximately one hour later when it syncs again. (BZ#1695550) -
In {product-title} 4.1,
ocandopenshift-installversion may have a dirtyGitTreeState:when checking theoc version. (BZ#1715001) -
In AWS environments, if a master node is stopped, the
kubeapiservercannot be deployed due a pod stuck in aPendingstatus. (BZ#1713292) -
All m4 instances on AWS fail to verify (CVE-2019-1109) using Broadwell CPU model 79 (type m4) because the
microcode_ctlwill not update. (BZ#1710981) -
New Elasticsearch deployments can not be created if another Elasticsearch deployment is stuck in a deleting state. (BZ#1711044)
-
There is no Open Java Console link available in the {product-title} 4.1 web console. (BZ#1713656)
-
The
openshift-cluster-node-tuning-operatormay generate a large number of secrets after several days of uptime. (BZ#1714484) -
Autoscaling for Memory Utilization is not working as expected. Creating HPA for memory-based autoscaling is failing while looking for resources. (BZ#1707785)
-
After successfully performing updates,
oc get clusterversionmay report that the update could not be applied. (BZ#1711964) -
The installer may have a
0return code when hitting a FATAL event. -
After disabling service catalog, attempting to delete projects on the cluster can get stuck in a "Terminating" state. This is caused by the service catalog API service not deleting itself properly, and the deletion hangs. Service catalog does not properly clean up service instance resources that have a
kubernetes-incubator/service-catalogfinalizer; as a result, the namespace controller cannot finish the namespace (project) deletion.A change was made to service catalog to prevent the hangs by no longer attempting to delete its API service after disabling service catalog. If you have any projects stuck in a "Terminating" state after deleting service catalog, cluster administrators can use the following workaround:
-
If you want to retain existing services that were deployed using service catalog, you must manually remove any
ownerReferencesfields in the secrets used by related service binding resources. Failure to do so results in the secrets being deleted along with the service bindings when the API service is removed, and applications may no longer be able to access the service.NoteThis step can be skipped if you do not want to retain the existing services. -
Manually delete the API service:
$ oc delete apiservice v1beta1.servicecatalog.k8s.io
After implementing this workaround, you can continue deleting projects without issue. (BZ#1746174)
-
Security, bug fix, and enhancement updates for {product-title} 4.1 are released as asynchronous errata through the Red Hat Network. All {product-title} 4.1 errata is available on the Red Hat Customer Portal. See the {product-title} Life Cycle for more information about asynchronous errata.
Red Hat Customer Portal users can enable errata notifications in the account settings for Red Hat Subscription Management (RHSM). When errata notifications are enabled, users are notified via email whenever new errata relevant to their registered systems are released.
|
Note
|
Red Hat Customer Portal user accounts must have systems registered and consuming {product-title} entitlements for {product-title} errata notification emails to generate. |
This section will continue to be updated over time to provide notes on enhancements and bug fixes for future asynchronous errata releases of {product-title} 4.1. Versioned asynchronous releases, for example with the form {product-title} 4.1.z, will be detailed in subsections. In addition, releases in which the errata text cannot fit in the space provided by the advisory will be detailed in subsections that follow.
|
Important
|
For any {product-title} release, always review the instructions on updating your cluster properly. |
Issued: 2019-06-04
{product-title} release 4.1 is now available. The list of packages included in the update are documented in the RHBA-2019:1173 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:0758 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
Issued: 2019-06-18
{product-title} release 4.1.2 is now available. The list of packages included in the update are documented in the RHBA-2019:1381 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:1382 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-06-26
{product-title} release 4.1.3 is now available. The list of packages included in the update are documented in the RHBA-2019:1590 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:1589 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-06-26
An update for ose-cluster-kube-apiserver-operator-container and ose-cluster-openshift-apiserver-operator-container is now available for {product-title} 4.1. Details of the update are documented in the RHSA-2019:1591 advisory.
Issued: 2019-07-03
An update for jenkins-2-plugins is now available for {product-title} 4.1. Details of the update are documented in the RHSA-2019:1636 advisory.
Issued: 2019-07-04
{product-title} release 4.1.4 is now available. The list of packages included in the update are documented in the RHBA-2019:1634 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:1635 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-07-17
{product-title} release 4.1.6 is now available. The list of packages included in the update are documented in the RHBA-2019:1767 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:1766 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-07-24
{product-title} release 4.1.7 is now available. The list of packages included in the update are documented in the RHBA-2019:1808 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:1809 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-07-31
{product-title} release 4.1.8 is now available. The list of packages included in the update are documented in the RHBA-2019:1865 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:1866 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-08-08
{product-title} release 4.1.9 is now available. The list of packages included in the update are documented in the RHBA-2019:2009 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:2010 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-08-14
{product-title} release 4.1.11 is now available. The list of packages included in the update are documented in the RHBA-2019:2416 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:2417 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-08-28
{product-title} release 4.1.13 is now available. The list of packages included in the update are documented in the RHBA-2019:2546 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:2547 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-09-10
{product-title} release 4.1.14 is now available. The list of packages included in the update are documented in the RHBA-2019:2660 advisory. The container images and bug fixes included in the update are provided by the RHSA-2019:2594 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-09-12
{product-title} release 4.1.15 is now available. The list of packages included in the update are documented in the RHBA-2019:2681 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:2680 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-09-20
{product-title} release 4.1.16 is now available. The list of packages included in the update are documented in the RHBA-2019:2794 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:2768 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-09-20
{product-title} release 4.1.17 is now available. The list of packages included in the update are documented in the RHBA-2019:2819 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:2820 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-09-27
{product-title} release 4.1.18 is now available. The list of packages included in the update are documented in the RHBA-2019:2855 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:2856 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-10-16
{product-title} release 4.1.20 is now available. The list of packages included in the update are documented in the RHBA-2019:3003 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:3004 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-10-30
{product-title} release 4.1.21 is now available. The list of packages included in the update are documented in the RHBA-2019:3153 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:3152 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-11-07
{product-title} release 4.1.22 is now available. The list of packages included in the update are documented in the RHBA-2019:3293 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:3294 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-11-12
{product-title} release 4.1.23 is now available. The list of packages included in the update are documented in the RHBA-2019:3766 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:3765 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-11-20
{product-title} release 4.1.24 is now available. The list of packages included in the update are documented in the RHBA-2019:3874 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:3875 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-11-27
{product-title} release 4.1.25 is now available. The list of packages included in the update are documented in the RHBA-2019:3912 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:3913 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-12-04
{product-title} release 4.1.26 is now available. The list of packages included in the update are documented in the RHBA-2019:3954 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:3956 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-12-17
{product-title} release 4.1.27 is now available. The list of packages included in the update are documented in the RHBA-2019:4083 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:4084 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2019-12-18
{product-title} release 4.1.28 is now available. The list of packages included in the update are documented in the RHBA-2019:4185 advisory. The container images and bug fixes included in the update are provided by the RHBA-2019:4186 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2020-01-08
{product-title} release 4.1.29 is now available. The list of packages included in the update are documented in the RHBA-2020:0009 advisory. The container images and bug fixes included in the update are provided by the RHBA-2020:0010 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2020-01-15
{product-title} release 4.1.30 is now available. The list of packages included in the update are documented in the RHBA-2020:0070 advisory. The container images and bug fixes included in the update are provided by the RHBA-2020:0071 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2020-01-22
{product-title} release 4.1.31 is now available. The list of packages included in the update are documented in the RHBA-2020:0114 advisory. The container images and bug fixes included in the update are provided by the RHBA-2020:0115 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2020-02-12
{product-title} release 4.1.34 is now available. The list of packages included in the update are documented in the RHBA-2020:0398 advisory. The container images and bug fixes included in the update are provided by the RHBA-2020:0399 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2020-03-12
{product-title} release 4.1.38 is now available. The list of packages included in the update are documented in the RHBA-2020:0690 advisory. The container images and bug fixes included in the update are provided by the RHBA-2020:0691 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2020-04-22
{product-title} release 4.1.41 is now available. The list of packages included in the update are documented in the RHBA-2020:1443 advisory. The container images and bug fixes included in the update are provided by the RHBA-2020:1446 advisory.
Space precluded documenting all of the container images for this release in the advisory. See the following article for notes on the container images in this release:
To upgrade an existing {product-title} 4.1 cluster to this latest release, see Updating a cluster by using the CLI for instructions.
Issued: 2020-04-22
An update for podman is now available for {product-title} 4.1. Details of the update are documented in the RHSA-2020:1449 advisory.
Issued: 2020-04-22
An update for openshift-enterprise-ansible-operator-container is now available for {product-title} 4.1. Details of the update are documented in the RHSA-2020:1545 advisory.
* indicate delivery in a z-stream patch.