1.4. Deprecated and removed features

The Jenkins Pipeline build strategy is now deprecated. You should use Jenkinsfiles directly on Jenkins or OpenShift Pipelines instead.

The apiextensions.k8s.io/v1beta1 API version for custom resource definitions (CRDs) is now deprecated. It will be removed in a future release of OpenShift Container Platform.

See v1 CRD support in Operator Lifecycle Manager for related details.

The flavor.template.kubevirt.io/Custom label is no longer used to identify Custom flavors.

The OperatorSource and CatalogSourceConfig objects have been deprecated for several OpenShift Container Platform releases. Starting in OpenShift Container Platform 4.4, if there are any custom OperatorSource or CatalogSourceConfig objects present on the cluster, the marketplace cluster Operator sets an Upgradeable=false condition and issues a Warning alert. This means that upgrades to OpenShift Container Platform 4.5 are blocked if the objects are still installed.

In OpenShift Container Platform 4.5, OperatorSource objects are still deprecated and only exist for the use of the default OperatorSource objects. CatalogSourceConfig objects, however, are now removed.

See the OpenShift Container Platform 4.4 release notes for how to convert OperatorSource and CatalogSourceConfig objects to use CatalogSource objects directly, which clears the alert and enables cluster upgrades to OpenShift Container Platform 4.5.

The v2 Ignition config spec is now deprecated for use when deploying new nodes as part of a fresh OpenShift Container Platform 4.6 installation. The v2 Ignition config spec is still supported for machine configurations.

If you have created custom Ignition v2 spec configurations to deploy new clusters, you must convert these to spec v3 when installing new OpenShift Container Platform 4.6 clusters. You should use the Ignition Config Converter tool to complete the conversion process. In general, v2 can be directly translated to v3. In certain edge cases, you might need to modify the output to make explicit configuration details that were assumed by spec v2.

The following oc commands and flags are affected:

The oc run command can now only be used to create pods. Use the oc create command instead to create other resources.

Service Catalog, Template Service Broker, Ansible Service Broker, and their associated Operators were deprecated starting in OpenShift Container Platform 4.2. Ansible Service Broker, including Ansible Service Broker Operator and related APIs and APBs, were removed in OpenShift Container Platform 4.4.

Service Catalog, Template Service Broker, and their associated Operators are now removed in OpenShift Container Platform 4.5, including the related .servicecatalog.k8s.io/v1beta1 API.

The service-catalog-controller-manager and service-catalog-apiserver cluster Operators were set to Upgradeable=false in 4.4. This means that they block cluster upgrades to the next minor version, 4.5 in this case, if they are still installed at that time. Upgrades to z-stream releases such as 4.4.z, however, are still permitted in this state.

If Service Catalog and Template Service Broker are enabled in 4.4, specifically if their management state is set to Managed, the web console warns cluster administrators that these features are still enabled. The following alerts can be viewed from the Monitoring Alerting page on a 4.4 cluster and have a Warning severity:

If they are still enabled on a 4.4 cluster, cluster administrators can see Uninstalling Service Catalog and Uninstalling Template Service Broker in the OpenShift Container Platform 4.4 documentation to uninstall it, which permits cluster upgrades to 4.5.

In 4.5, a pair of jobs are created in a new openshift-service-catalog-removed namespace to run during the cluster upgrade process. Their behavior depends on the management state of Service Catalog:

The jobs and openshift-service-catalog-removed namespace will be removed in a future OpenShift Container Platform release.

CatalogSourceConfig objects are now removed. See OperatorSource and CatalogSourceConfig objects block cluster upgrades for more details.

The following images are no longer included in the samples imagestreams provided with OpenShift Container Platform:

registry.redhat.io/dotnet/dotnet-30-rhel7:3.0
registry.redhat.io/dotnet/dotnet-30-runtime-rhel7:3.0
registry.redhat.io/openjdk/openjdk-11-rhel8:1.1
registry.redhat.io/rhoar-nodejs-tech-preview/rhoar-nodejs-10-webapp
registry.redhat.io/rhscl/mongodb-32-rhel7
registry.redhat.io/rhscl/python-35-rhel7
registry.redhat.io/rhdm-7/rhdm-decisioncentral-rhel8:7.5.1
registry.redhat.io/rhdm-7/rhdm-kieserver-rhel8:7.5.0
registry.redhat.io/rhdm-7/rhdm-kieserver-rhel8:7.5.1
registry.redhat.io/rhdm-7-tech-preview/rhdm-optaweb-employee-rostering-rhel8:7.5.0
registry.redhat.io/rhdm-7-tech-preview/rhdm-optaweb-employee-rostering-rhel8:7.5.1
registry.redhat.io/rhpam-7/rhpam-businesscentral-monitoring-rhel8:7.5.0
registry.redhat.io/rhpam-7/rhpam-businesscentral-monitoring-rhel8:7.5.1
registry.redhat.io/rhpam-7/rhpam-businesscentral-rhel8:7.5.0
registry.redhat.io/rhpam-7/rhpam-businesscentral-rhel8:7.5.1
registry.redhat.io/rhpam-7/rhpam-kieserver-rhel8:7.5.0
registry.redhat.io/rhpam-7/rhpam-kieserver-rhel8:7.5.1
registry.redhat.io/rhpam-7/rhpam-smartrouter-rhel8:7.5.0
registry.redhat.io/rhpam-7/rhpam-smartrouter-rhel8:7.5.1
registry.redhat.io/rhscl/ruby-23-rhel7

The Amazon Web Services (AWS) Elastic File System (EFS) Technology Preview feature has been removed and is no longer supported.