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

Service, ReplicaSet, Job, and ReplicationController list views are missing their Pod Selector column

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Unresolved
    • Icon: Normal Normal
    • None
    • 4.21
    • Management Console
    • None
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • Low
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None
    • None

      Several Kubernetes workload resources that use pod selectors are missing the Pod Selector column in their list views, creating an inconsistent user experience. While these resources display pod selectors in their detail
      pages, users cannot see or click pod selectors directly from the search/list view.

      Affected Resources

      1. Service
      2. ReplicaSet
      3. Job
      4. ReplicationController 

       

      Current Behavior

      • Users can see pod selectors in the Details tab of these resources
      • Pod selectors are NOT visible in the list/search table views
      • Users cannot click pod selectors to navigate to matching pods from the list view

      Expected Behavior

      • Pod Selector column should be displayed in list/search tables (similar to Service, Deployment, StatefulSet, DaemonSet, and DeploymentConfig)
      • Pod selectors should be clickable links that navigate to /search/ns/<namespace>?kind=Pod&q=<selector> with the appropriate label filters applied

      Inconsistency

      Other workload resources already have clickable Pod Selector columns in their list views:

      • ✅ Deployment
      • ✅ StatefulSet
      • ✅ DaemonSet
      • ✅ DeploymentConfig

      Impact

      • Usability: Users must navigate to detail pages to see pod selectors instead of seeing them at a glance in list views
      • Workflow inefficiency: Cannot quickly navigate from resource list to filtered pods with a single click
      • Inconsistent UX: Different workload types behave differently without clear reasoning

              sgoodwin_redhat Steve goodwin
              sgoodwin_redhat Steve goodwin
              None
              None
              YaDan Pei YaDan Pei
              None
              Votes:
              0 Vote for this issue
              Watchers:
              2 Start watching this issue

                Created:
                Updated: