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

Fuse console project selector to exclude any openshift* projects by default (ootb)

    XMLWordPrintable

Details

    • Enhancement
    • Resolution: Not a Bug
    • Major
    • None
    • fuse-7.8-GA
    • Fuse Console, Fuse on Openshift
    • None
    • False
    • False
    • % %
    • +
    • Undefined
    • Fuse On Openshift

    Description

      With the work done in ENTESB-14539 it is possible to define a selector in the Fuse console to specifically configure which OpenShift namespaces to check for Fuse applications.

      In OCP 4.x there are some 15+ openshift-* namespaces created by OCP itself.

      The request here is to configure the Fuse console out of the box to exclude any openshift-* namespaces when looking for Fuse pods. This should be done in a way so that users can modify this exclusion filter again if really needed (which should barely be the case). This was already discussed here.

      Attachments

        Issue Links

          relates to

          Enhancement - An enhancement to or refactoring of existing functionality that is not configurable by an end user (typically a change made by an internal team that affects users) ENTESB-14539 Fuse 7 OpenShift console should support a per-network zone deployment model

          • Major - To be worked after higher priority work items are addressed. When the severity is high and the effort to change it is low to moderate, this term is chosen. Issues in this category likely have an existing workaround but implementation or execution may be non-trivial.
          • Done

          Activity

            People

              Unassigned Unassigned
              rhn-support-tmielke Torsten Mielke
              Juri Solovjov Juri Solovjov
              Votes:
              0 Vote for this issue
              Watchers:
              3 Start watching this issue

              Dates

                Created:
                Updated:
                Resolved: