Chapter 5. Preparing to update to OpenShift Container Platform 4.12

• 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
  ...
  poddisruptionbudgets.v1.policy                                                               391                     8114
  poddisruptionbudgets.v1beta1.policy                                       1.25               2                       23
  podmonitors.v1.monitoring.coreos.com                                                         3                       70
  podnetworkconnectivitychecks.v1alpha1.controlplane.operator.openshift.io                     612                     11748
  pods.v1                                                                                      1531                    38634
  podsecuritypolicies.v1beta1.policy                                        1.25               3                       39
  podtemplates.v1                                                                              2                       79
  preprovisioningimages.v1alpha1.metal3.io                                                     2                       39
  priorityclasses.v1.scheduling.k8s.io                                                         12                      248
  prioritylevelconfigurations.v1beta1.flowcontrol.apiserver.k8s.io          1.26               3                       86
  ...

  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.26	flowschemas.v1beta1.flowcontrol.apiserver.k8s.io
  1.26	horizontalpodautoscalers.v2beta2.autoscaling
  1.25	poddisruptionbudgets.v1beta1.policy
  1.25	podsecuritypolicies.v1beta1.policy
  1.26	prioritylevelconfigurations.v1beta1.flowcontrol.apiserver.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 poddisruptionbudgets.v1beta1.policy -o yaml

  You can also use

  -o jsonpath

  to extract the

  username

  and

  userAgent

  values from an

  APIRequestCount

  resource:

  $ oc get apirequestcounts poddisruptionbudgets.v1beta1.policy \
    -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  system:serviceaccount:openshift-operators:3scale-operator                      manager/v0.0.0
  watch  system:serviceaccount:openshift-operators:datadog-operator-controller-manager  manager/v0.0.0