Feature Overview

Goals

Support partial matches and wildcards.

Example:

• namespace: openshift-*
• namespace: !=openshift-*

Acceptance Criteria:

• Syntax will be modeled after Posgres LIKE.

Requirements

..
 

(Optional) Use Cases

This Section:

• We need to be able to use `namespace:!=openshift-*` in search, so we can exclude objects
• We need to be able to use `namespace:openshift-*` in search, so we can include a range of objects.

Background, and strategic fit

This Section: What does the person writing code, testing, documenting
need to know? What context can be provided to frame this feature?

Documentation Considerations

Questions to be addressed:

• What educational or reference material (docs) is required to support this
  product feature? For users/admins? Other functions (security officers, etc)?
• Does this feature have a doc impact?
• New Content, Updates to existing content, Release Note, or No Doc Impact
• If unsure and no Technical Writer is available, please contact Content
  Strategy.
• What concepts do customers need to understand to be successful in
  [action]?
• How do we expect customers will use the feature? For what purpose(s)?
• What reference material might a customer want/need to complete [action]?
• Is there source material that can be used as reference for the Technical
  Writer in writing the content? If yes, please link if available.
• What is the doc impact (New Content, Updates to existing content, or
  Release Note)?