Uploaded image for project: 'OpenShift Logging'
  1. OpenShift Logging
  2. LOG-3427

Dev console uses cluster-scoped instead of namespace-scoped resource queries for filters

    XMLWordPrintable

Details

    • False
    • None
    • False
    • NEW
    • VERIFIED
    • Before this change the dev console used cluster scoped queries instead of namespace scoped queries for filters. This change uses the correct scope and displays an error message when the user has no permission over the current namespace resources.
    • Log Storage - Sprint 229

    Description

      Description of problem:

      When a non-admin user selects a filter from the dropdown that includes pods or containers, it uses the cluster scoped API. This leads to an error as most non-admin users won't have permission over broad set of resources

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

      OCP 4.12
      Logging 5.6

      How reproducible:

      Always

      Steps to Reproduce:

      1. Enable Console plugin
      2. Create test projects using normal user
      3. Login to Openshift console as a normal user
      4. Switch to Developer mode
      5. Go to 'Aggregated logs' in 'Observe' menu
      6. In the filter Dropdown select "Pods" and click on "Filter by pod"

      Actual results:

      Error if the user does not have cluster-scoped list pods permission

      Expected results:

      No error when the user has namespace-scoped permissions to list pods

       

      Attachments

        Activity

          People

            gbernal@redhat.com Gabriel Bernal
            gbernal@redhat.com Gabriel Bernal
            Giriyamma Karagere Ramaswamy Giriyamma Karagere Ramaswamy (Inactive)
            Votes:
            1 Vote for this issue
            Watchers:
            3 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: