Uploaded image for project: 'OpenShift Bugs'
  1. OpenShift Bugs
  2. OCPBUGS-31358

kube-controller-manager doesn't check for resource presence when deleting legacy providers

    XMLWordPrintable

Details

    • No
    • False
    • Hide

      None

      Show
      None

    Description

      Description of problem:

          kube-controller-manager operator is cleaning up resources for legacy in-tree controllers, running multiple delete requests to apiserver. 
      This has several drawbacks:
      * API Server can't cache DELETE requests, so it has to request etcd every time
      * Audit log is flooded with "delete failed: object 'foo' not found" record
      The function should first check that the object exists (GET requests are cachable) before issuing a DELETE request

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

          

      How reproducible:

          

      Steps to Reproduce:

          1.
          2.
          3.
          

      Actual results:

          

      Expected results:

          

      Additional info:

          

      Attachments

        Activity

          People

            rh-ee-nbrubake Nolan Brubaker
            vrutkovs@redhat.com Vadim Rutkovsky
            Zhaohua Sun Zhaohua Sun
            Votes:
            0 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated: