Skip to content

OCPBUGS-33123: update matchLabels values to strings #95249

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 1 commit into from

Conversation

@openshift-ci-robot
Copy link

@jldohmann: This pull request references Jira Issue OCPBUGS-33123, which is invalid:

  • expected the bug to target the "4.20.0" version, but no target version was set

Comment /jira refresh to re-evaluate validity if changes to the Jira bug are made, or edit the title of this pull request to link to a different bug.

The bug has been updated to refer to the pull request using the external bug tracker.

In response to this:

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OCPBUGS-33123

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

@openshift-ci openshift-ci bot added the size/S Denotes a PR that changes 10-29 lines, ignoring generated files. label Jun 25, 2025
@jldohmann
Copy link
Contributor Author

@lihongan could you PTAL at this docs PR for QE ack? this PR updates the values for matchLabels fields to be strings. thank you 🙇

@ocpdocs-previewbot
Copy link

Copy link

openshift-ci bot commented Jun 25, 2025

@jldohmann: all tests passed!

Full PR test history. Your PR dashboard.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository. I understand the commands that are listed here.

@jldohmann jldohmann added peer-review-needed Signifies that the peer review team needs to review this PR labels Jun 25, 2025
@lihongan
Copy link

@jldohmann I add comment to the bug, indeed we don't need add " for the value of matchLabels.
There are two ways to set namespaceSelector or routeSelector, one is using matchLabels and it looks like

spec:
  namespaceSelector:
    matchLabels:
      name: dev

Another is using matchExpressions and it looks like

spec:
  namespaceSelector:
    matchExpressions:
    - key: name
      operator: In
      values:
      - dev
      - ops

But the wrong example is:

spec:
  namespaceSelector:
    matchLabels:
      name:
        - finance
        - ops

@lahinson lahinson added peer-review-in-progress Signifies that the peer review team is reviewing this PR and removed peer-review-needed Signifies that the peer review team needs to review this PR labels Jun 26, 2025
Copy link
Contributor

@lahinson lahinson left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Just one question for you. Otherwise, LGTM!

@@ -26,7 +26,7 @@ spec:
- ops
----

An example of a configured Ingress Controller `dev-router` that has the label selector `spec.namespaceSelector.matchLabels.name` with the key value set to `dev`:
An example of a configured Ingress Controller `dev-router` that has the label selector `spec.namespaceSelector.matchLabels.name` with the key value set to `"dev"`:
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should the phrase "label selector" follow spec.namespaceSelector.matchLabels.name? For example, "...that has the spec.namespaceSelector.matchLabels.name label selector with the key value set to "dev":"

@lahinson lahinson added peer-review-done Signifies that the peer review team has reviewed this PR and removed peer-review-in-progress Signifies that the peer review team is reviewing this PR labels Jun 26, 2025
@jldohmann
Copy link
Contributor Author

thank you Hongan, I think i'll close this PR and open a new one since I need to change the base branch anyway

@jldohmann jldohmann closed this Jun 26, 2025
@jldohmann jldohmann deleted the OCPBUGS-33123 branch June 26, 2025 17:56
@openshift-ci-robot
Copy link

@jldohmann: This pull request references Jira Issue OCPBUGS-33123. The bug has been updated to no longer refer to the pull request using the external bug tracker. All external bug links have been closed. The bug has been moved to the NEW state.

In response to this:

Version(s): 4.12+

Issue: https://issues.redhat.com/browse/OCPBUGS-33123

Link to docs preview:

QE review:

  • QE has approved this change.

Additional information:

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the openshift-eng/jira-lifecycle-plugin repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
branch/enterprise-4.12 branch/enterprise-4.13 branch/enterprise-4.14 branch/enterprise-4.15 branch/enterprise-4.16 branch/enterprise-4.17 branch/enterprise-4.18 branch/enterprise-4.19 branch/enterprise-4.20 jira/invalid-bug Indicates that a referenced Jira bug is invalid for the branch this PR is targeting. jira/valid-reference Indicates that this PR references a valid Jira ticket of any type. peer-review-done Signifies that the peer review team has reviewed this PR size/S Denotes a PR that changes 10-29 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants