Uploaded image for project: 'Red Hat Fuse'
  1. Red Hat Fuse
  2. ENTESB-11962

Operator does not revert manual changes to properties it does not know about

XMLWordPrintable

    • % %
    • Hide

      1. deploy syndesis
      2. oc get -o json dc syndesis-ui | jq '.spec.template.spec.containers[0].resources' will not have a cpu entry under requests
      3. edit the syndesis-ui dc and add the cpu entry under requests, setting a value smaller than the limit
      4. notice the ui pod gets redeployed
      5. oc get -o json dc syndesis-ui | jq '.spec.template.spec.containers[0].resources' now shows the limit we set
      6. the limit in the pod is also set accordingly

      Show
      1. deploy syndesis 2. oc get -o json dc syndesis-ui | jq '.spec.template.spec.containers[0].resources' will not have a cpu entry under requests 3. edit the syndesis-ui dc and add the cpu entry under requests , setting a value smaller than the limit 4. notice the ui pod gets redeployed 5. oc get -o json dc syndesis-ui | jq '.spec.template.spec.containers[0].resources' now shows the limit we set 6. the limit in the pod is also set accordingly

      When an openshift resource is manually edited and a property is added that was not created by the operator, the operator notices the changes and updates resources affected by that change and will not revert to the previous state.

      Found for the case of adding a cpu to resource limits, but assuming same thing will happen for other such properties

              Unassigned Unassigned
              asmigala@redhat.com Andrej Smigala
              Votes:
              0 Vote for this issue
              Watchers:
              4 Start watching this issue

                Created:
                Updated:
                Resolved: