Backport is merged so marking as modified. RE: https://github.com/openshift/cluster-monitoring-operator/pull/305

Tested with cluster-monitoring-operator-v3.11.104-1, KubeletTooManyPods rule is under below, since the maximum pods number is 250, this alert will not be triggered, and message "close to the limit of 110" is also wrong, should be 250
*************************************** 
    - alert: KubeletTooManyPods
      annotations:
        message: Kubelet {{$labels.instance}} is running {{$value}} pods, close to
          the limit of 110.
      expr: |
        kubelet_running_pod_count{job="kubelet"} > 250
      for: 15m
      labels:
        severity: warning
***************************************

Should be the same with 4.1 KubeletTooManyPods rule
***************************************
    - alert: KubeletTooManyPods
      annotations:
        message: Kubelet {{ $labels.instance }} is running {{ $value }} Pods, close
          to the limit of 250.
      expr: |
        kubelet_running_pod_count{job="kubelet"} > 250 * 0.9
      for: 15m
      labels:
        severity: warning
***************************************

Good catch! https://github.com/openshift/cluster-monitoring-operator/pull/317 fixes this.

https://github.com/openshift/cluster-monitoring-operator/pull/317 is merged, so moving to modified again.

Tested with cluster-monitoring-operator-v3.11.105-1, issue is fixed

alert: KubeletTooManyPods
expr: kubelet_running_pod_count{job="kubelet"}
  > 250 * 0.9
for: 15m
labels:
  severity: warning
annotations:
  message: Kubelet {{ $labels.instance }} is running {{ $value }} Pods, close to the
    limit of 250.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2019:0794