Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-2618

Logging uses deprecated v1beta1 apis

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Logging (Core) - Sprint 219, Logging (Core) - Sprint 220

    Description

      Description of problem:

      CLO triggers alert `APIRemovedInNextEUSReleaseInUse` in OCP 4.11:

      $ token=`oc sa get-token prometheus-k8s -n openshift-monitoring`
      $ oc -n openshift-monitoring exec -c prometheus prometheus-k8s-0 -- curl -sk -H "Authorization: Bearer $token" 'https://prometheus-k8s.openshift-monitoring.svc:9091/api/v1/query?' --data-urlencode 'query=ALERTS{alertname="APIRemovedInNextEUSReleaseInUse"}' | jq
      {
        "status": "success",
        "data": {
          "resultType": "vector",
          "result": [
            {
              "metric": {
                "__name__": "ALERTS",
                "alertname": "APIRemovedInNextEUSReleaseInUse",
                "alertstate": "pending",
                "group": "batch",
                "namespace": "openshift-kube-apiserver",
                "resource": "cronjobs",
                "severity": "info",
                "version": "v1beta1"
              },
              "value": [
                1652337084.771,
                "1"
              ]
            }
          ]
        }
      } 
      $ oc get apirequestcounts cronjobs.v1beta1.batch -o yaml
      apiVersion: apiserver.openshift.io/v1
      kind: APIRequestCount
      metadata:
        creationTimestamp: "2022-05-12T06:01:08Z"
        generation: 1
        name: cronjobs.v1beta1.batch
        resourceVersion: "75983"
        uid: 136d1844-e71c-4952-a9d9-279bad09ba18
      spec:
        numberOfUsersToReport: 10
      status:
        currentHour:
          byNode:
          - byUser:
            - byVerb:
              - requestCount: 36
                verb: delete
              requestCount: 36
              userAgent: cluster-logging-operator/v0.0.0
              username: system:serviceaccount:openshift-logging:cluster-logging-operator
            nodeName: 172.31.246.15
            requestCount: 36
          requestCount: 36
      ......
        removedInRelease: "1.25"
        requestCount: 47

      Version-Release number of selected component (if applicable):

      ClusterVersion: 4.11.0-0.nightly-2022-05-11-054135

      CSV: cluster-logging.5.4.1-26 

      How reproducible:

      Always

      Steps to Reproduce:
      1. deploy CLO and EO on OCP 4.11
      2. create clusterlogging/instance with:

      apiVersion: "logging.openshift.io/v1"
      kind: "ClusterLogging"
      metadata:
        name: "instance"
        namespace: "openshift-logging"
      spec:
        managementState: "Managed"
        logStore:
          type: "elasticsearch"
          retentionPolicy: 
            application:
              maxAge: 1d
            infra:
              maxAge: 3h
            audit:
              maxAge: 2w
          elasticsearch:
            nodeCount: 3
            redundancyPolicy: "SingleRedundancy"
            resources:
              requests:
                memory: "2Gi"
            storage:
              storageClassName: "thin"
              size: "20Gi"
        visualization:
          type: "kibana"
          kibana:
            replicas: 1
        collection:
          logs:
            type: "fluentd"
            fluentd: {}

      3. check alerts on OCP console

      Actual results:Expected results:

      Additional info: 

      Attachments

        Activity

          People

            jcantril@redhat.com Jeffrey Cantrill
            qitang@redhat.com Qiaoling Tang
            Qiaoling Tang Qiaoling Tang
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: