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

Fuse console operator installed from Operator Hub does not define resource requests or limits

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Done
    • Icon: Major Major
    • fuse-7.11-GA
    • fuse-7.10-GA
    • Fuse Console
    • None
    • False
    • None
    • False
    • % %
    • +
    • Automated
    • Hide

      Edit the operator's YAML manually after installation, and insert the required resource definition.

      Show
      Edit the operator's YAML manually after installation, and insert the required resource definition.
      • Install the Fuse 7.10 version of the the Fuse console using the Operator Hub
      • Inspect the YAML of the resulting deployment

      If the Fuse console operator is installed from the Operator Hub, no resources are defined in the resulting deployment object. The resources section is completely empty. Some installations of OCP require that all deployments specify resource requests and limits; failing to do so makes the operator hard to install.

      The manual installation procedure described in the documentation [1] does get resource requests and limits, so this seems to be a problem specific to the use of the Operator Hub.

      [1] https://access.redhat.com/documentation/en-us/red_hat_fuse/7.10/html/managing_fuse_on_openshift/fuse-console-setup-openshift4#fuse-console-install-openshift4-commandline

       

              mmelko@redhat.com Matej Melko
              rhn-support-kboone Kevin Boone
              Juri Solovjov Juri Solovjov
              Votes:
              0 Vote for this issue
              Watchers:
              7 Start watching this issue

                Created:
                Updated:
                Resolved: