Uploaded image for project: 'OpenShift Pipelines'
  1. OpenShift Pipelines
  2. SRVKP-3049

[1.9.3] - Remove Deprecated API from OpenShift Pipelines

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Won't Do
    • Icon: Normal Normal
    • Pipelines 1.9.4
    • None
    • Operator
    • None
    • 1
    • False
    • None
    • False
    • Pipelines Sprint 239, Pipelines Sprint 240, Pipelines Sprint 252

      Description of problem:

      Deprecated APIs that are no longer in use should not be included or alerted on in OpenShift Pipelines.

      Prerequisites (if any, like setup, operators/versions):

      OpenShift 4.11
      OpenShift Pipelines 1.9, 1.10

      Steps to Reproduce

      The console is report these depericated APIs.
      In the OpenShift cluster, the following PodSecurityPolicies are installed:
      tekton-pipelines
      tekton-triggers
      The PodSecurityPolicy API is deprecated since OCP 4.8 (Kubernetes v1.21) and will be removed in a future OCP version (Kubernetes v1.25). The OpenShift cluster load also increases disproportionately when PodSecurityPolicies are used.

      Deprecated API that will be removed in the next EUS version is being used
      Removing the workload that is using the...

       

      Actual results:

      Receiving Depericated alerts in OCP 4.10 on Pipelines version 1.6.4

      Expected results:

      I was told you will no longer receive deprecated API Iin alerts in 1.9 and 1.10. However, we should also remove deprecated APIs that are no longer in use from OpenShift Pipelines.

      Reproducibility (Always/Intermittent/Only Once):

      Always alerts on OCP 4.10 on Pipelines 1.6.4.

              piyushgarg001 Piyush Garg
              rhn-support-bsmitley Brandon Smitley
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

                Created:
                Updated:
                Resolved: