Chapter 4. Preparing to update to OpenShift Container Platform 4.9

• APIRemovedInNextReleaseInUse - for APIs that will be removed in the next OpenShift Container Platform release.
• APIRemovedInNextEUSReleaseInUse - for APIs that will be removed in the next OpenShift Container Platform Extended Update Support (EUS) release.

Prerequisites

• You must have access to the cluster as a user with the cluster-admin role.

Procedure

• Run the following command and examine the REMOVEDINRELEASE column of the output to identify the removed APIs that are currently in use:

  $ oc get apirequestcounts

  Example output

  NAME                                        REMOVEDINRELEASE   REQUESTSINCURRENTHOUR   REQUESTSINLAST24H
  cloudcredentials.v1.operator.openshift.io                      32                      111
  ingresses.v1.networking.k8s.io                                 28                      110
  ingresses.v1beta1.extensions                1.22               16                      66
  ingresses.v1beta1.networking.k8s.io         1.22               0                       1
  installplans.v1alpha1.operators.coreos.com                     93                      167
  ...

  Important

  You can safely ignore the following entries that appear in the results:

  • The system:serviceaccount:kube-system:generic-garbage-collector and the system:serviceaccount:kube-system:namespace-controller users might appear in the results because these services invoke all registered APIs when searching for resources to remove.
  • The system:kube-controller-manager and system:cluster-policy-controller users might appear in the results because they walk through all resources while enforcing various policies.

  You can also use -o jsonpath to filter the results:

  $ oc get apirequestcounts -o jsonpath='{range .items[?(@.status.removedInRelease!="")]}{.status.removedInRelease}{"\t"}{.metadata.name}{"\n"}{end}'

  Example output

  1.22    certificatesigningrequests.v1beta1.certificates.k8s.io
  1.22    ingresses.v1beta1.extensions
  1.22    ingresses.v1beta1.networking.k8s.io

Prerequisites

• You must have access to the cluster as a user with the cluster-admin role.

Procedure

• Run the following command and examine the username and userAgent fields to help identify the workloads that are using the API:

  $ oc get apirequestcounts <resource>.<version>.<group> -o yaml

  For example:

  $ oc get apirequestcounts ingresses.v1beta1.networking.k8s.io -o yaml

  You can also use -o jsonpath to extract the username and userAgent values from an APIRequestCount resource:

  $ oc get apirequestcounts ingresses.v1beta1.networking.k8s.io \
    -o jsonpath='{range .status.currentHour..byUser[*]}{..byVerb[*].verb}{","}{.username}{","}{.userAgent}{"\n"}{end}' \
    | sort -k 2 -t, -u | column -t -s, -NVERBS,USERNAME,USERAGENT

  Example output

  VERBS  USERNAME                        USERAGENT
  watch  bob                             oc/v4.8.11
  watch  system:kube-controller-manager  cluster-policy-controller/v0.0.0