1.4. Deprecated and removed features

Some features available in previous releases have been deprecated or removed.

Deprecated functionality is still included in OpenShift Container Platform and continues to be supported; however, it will be removed in a future release of this product and is not recommended for new deployments. For the most recent list of major functionality deprecated and removed within OpenShift Container Platform 4.5, refer to the table below. Additional details for more fine-grained functionality that has been deprecated and removed are listed after the table.

In the table, features are marked with the following statuses:

  • GA: General Availability
  • DEP: Deprecated
  • REM: Removed

표 1.1. Deprecated and removed features tracker

FeatureOCP 4.3OCP 4.4OCP 4.5

Service Catalog

DEP

DEP

REM

Template Service Broker

DEP

DEP

REM

OpenShift Ansible Service Broker

DEP

REM

REM

OperatorSources

DEP

DEP

DEP

CatalogSourceConfigs

DEP

DEP

REM

Operator Framework’s Package Manifest Format

GA

DEP

DEP

v1beta1 CRDs

GA

GA

DEP

1.4.1. Deprecated features

1.4.1.1. Jenkins Pipeline build strategy

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

1.4.1.2. v1beta1 CRDs

The apiextensions.k8s.io/v1beta1 API version for CustomResourceDefinitions (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.

1.4.1.3. Custom label no longer in use

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

1.4.1.4. OperatorSources and CatalogSourceConfigs block cluster upgrades

OperatorSources and CatalogSourceConfigs have been deprecated for several OpenShift Container Platform releases. Starting in OpenShift Container Platform 4.4, if there are any custom OperatorSources or CatalogSourceConfigs 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.

참고

Upgrades to OpenShift Container Platform 4.4 z-stream releases are still permitted in this state.

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

See the OpenShift Container Platform 4.4 release notes for how to convert OperatorSources and CatalogSourceConfigs to using CatalogSources directly, which clears the alert and enables cluster upgrades to OpenShift Container Platform 4.5.

1.4.2. Removed features

1.4.2.1. OpenShift CLI commands and flags removed

The following oc commands and flags are affected:

  • The oc policy can-i command was deprecated in OpenShift Container Platform 3.9 and has been removed. You must use oc auth can-i instead.
  • The --image flag previously used for the oc new-app and oc new-build commands was deprecated in OpenShift Container Platform 3.2 and has been removed. You must use the --image-stream flag with these commands instead.
  • The --list flag previously used in the oc set volumes command was deprecated in OpenShift Container Platform 3.3 and has been removed. The oc set volumes lists volumes without a flag.
  • The -t flag previously used in the oc process command was deprecated in OpenShift Container Platform 3.11 and has been removed. You must use the --template flag with this command instead.
  • The --output-version flag previously used in the oc process command was deprecated in OpenShift Container Platform 3.11 and has been removed. This flag was already ignored.
  • The -v flag previously used in the oc set deployment-hook command was deprecated in OpenShift Container Platform 3.11 and has been removed. You must use the --volumes flag with this command instead.
  • The -v and --verbose flags previously used in the oc status command were deprecated in OpenShift Container Platform 3.11 and have been removed. You must use the --suggest flag with this command instead.

1.4.2.2. The oc run OpenShift CLI command now only creates Pods

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

1.4.2.3. Service Catalog, Template Service Broker, and their Operators

중요

Service Catalog is not installed by default in OpenShift Container Platform 4; however, it now blocks upgrades to OpenShift Container Platform 4.5 if installed.

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.

참고

Templates are still available in OpenShift Container Platform 4.5, but they are no longer handled by Template Service Broker. By default, the Samples Operator handles Red Hat Enterprise Linux (RHEL)-based OpenShift Container Platform ImageStreams and Templates. See Configuring the Samples Operator for details.

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:

  • ServiceCatalogAPIServerEnabled
  • ServiceCatalogControllerManagerEnabled
  • TemplateServiceBrokerEnabled

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:

  • Removed: The Jobs remove the following Service Catalog items:

    • Operators
    • namespaces
    • Custom Resources (CRs)
    • ClusterRoles
    • ClusterRoleBindings
  • Unmanaged: The Jobs skip removal and do nothing.
  • Managed: The Jobs report an error in logs. This state is unlikely to occur because upgrades would have been blocked. The Jobs take no other actions.

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

참고

As of OpenShift Container Platform 4.5, all Red Hat-provided service brokers have been removed. Any other broker installed by users is not removed by the upgrade process. This is to avoid removing any services that might have been deployed using the brokers. Users must remove these brokers manually.

1.4.2.4. CatalogSourceConfigs removed

CatalogSourceConfigs are now removed. See OperatorSources and CatalogSourceConfigs block cluster upgrades for more details.