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

resetting an operator to managed once again after having been Unmanaged does not return to the desired state

XMLWordPrintable

    • None
    • False
    • Hide

      None

      Show
      None

      Description of problem:

      
      while we know that setting an operator as Unmamaged is not a supported operation, it would be desirable that CVO would reset settings once the "overrides" is removed.
      
      For instance, if I set this in the CVO:
      
      spec:
        overrides:
        - group: apps
          kind: Deployment
          name: some-operator
          namespace: the-operator-namespace
          unmanaged: true
      
      and after that, the deployment is scaled to 0 manually, I would like to see cluster version operator re-scaled to the original value once the former paragraph is deleted.
      
      I was going to set this as RFE because of the reason I have given ( setting as unmanaged is unsupported operation ).
      
      The justification for this is that we don't have much trace if a customer does this and reset the configuration and we could find the cluster in a status is not normal even if everything is configured as expected. Only audit logs could help to understand what has happened.
      
      Thanks in advance.
      
          

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

       4.16
      
          

            Unassigned Unassigned
            rhn-support-gparente German Parente
            Jia Liu Jia Liu
            Votes:
            0 Vote for this issue
            Watchers:
            5 Start watching this issue

              Created:
              Updated: