Prometheus adapter reports "unable to fetch CPU metrics" for completed and succeeded pods

Issue

• Errors reported in prometheus-adapter pod:

2021-02-02T10:32:33.834320370Z E0202 10:32:33.834317       1 provider.go:187] unable to fetch CPU metrics for pod openshift-kube-apiserver/revision-pruner-16-ip-10-0-162-147.eu-central-1.compute.internal, skipping
2021-02-02T10:32:33.834328262Z E0202 10:32:33.834322       1 provider.go:187] unable to fetch CPU metrics for pod openshift-kube-apiserver/revision-pruner-16-ip-10-0-202-64.eu-central-1.compute.internal, skipping
2021-02-02T10:32:33.834335182Z E0202 10:32:33.834327       1 provider.go:187] unable to fetch CPU metrics for pod openshift-kube-apiserver/revision-pruner-17-ip-10-0-156-87.eu-central-1.compute.internal, skipping
2021-02-02T10:32:33.834335182Z E0202 10:32:33.834331       1 provider.go:187] unable to fetch CPU metrics for pod openshift-kube-apiserver/revision-pruner-17-ip-10-0-162-147.eu-central-1.compute.internal, skipping
2021-02-02T10:32:33.834342408Z E0202 10:32:33.834336       1 provider.go:187] unable to fetch CPU metrics for pod openshift-kube-apiserver/revision-pruner-17-ip-10-0-202-64.eu-central-1.compute.internal, skipping
2021-02-02T10:32:33.834349227Z E0202 10:32:33.834340       1 provider.go:187] unable to fetch CPU metrics for pod openshift-kube-apiserver/revision-pruner-18-ip-10-0-156-87.eu-central-1.compute.internal, skipping
2021-02-02T10:32:33.834349227Z E0202 10:32:33.834345       1 provider.go:187] unable to fetch CPU metrics for pod openshift-kube-apiserver/revision-pruner-19-ip-10-0-156-87.eu-central-1.compute.internal, skipping