Skip to content
This repository has been archived by the owner on Jan 19, 2023. It is now read-only.
This repository has been archived by the owner on Jan 19, 2023. It is now read-only.

Expression filters are not rendered correctly #2252

Closed
@xtreme-jon-ji

Description

What steps did you take and what happened:

  1. Apply a deployment that contains a matchExpressions selector. Example:
---
apiVersion: apps/v1
kind: Deployment
metadata:
  name: nginx
spec:
  selector:
    matchLabels:
      labelA: someLabelA
    matchExpressions:
      - key: labelB
        operator: In
        values:
          - someLabelB
  template:
    metadata:
      labels:
        labelA: someLabelA
        labelB: someLabelB
    spec:
      containers:
        - image: nginx
          name: nginx
  1. Navigate to Namespace Overview, or any screen where deployments are listed
  2. See values in the Selector column - they appear as: labelA:someLabelA and labelB:

Screenshot 2021-03-31 at 2 42 10 PM

What did you expect to happen:

  1. The expression selector should be rendered as: labelB In someLabelB

Anything else you would like to add:
It looks like the selectors type is being rendered as an OverflowSelectorsComponent, which is treating each selector as a label selector.

Environment:
Octant version: 0.18.0

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions