Filtering & Search

Kunobi's filter bar lets you quickly narrow down any resource list using a simple but powerful syntax. You can filter by kind, namespace, field values, regex patterns, or exact matches — negate any condition, and save your favorite filters as presets.

Opening the Filter Bar

• Click the search/filter icon in the toolbar, or
• Press ⌘F (macOS) / Ctrl+F (Windows/Linux) to focus the filter input

Filter Syntax

Plain Text (Name Filter)

Type any text to filter resources by name. Plain text uses fuzzy matching by default — you don't need to type the exact substring.

nginx

Shows all resources whose name matches nginx.

Scoring priority: exact match scores highest, followed by substring match, then word-start match (matching the beginning of hyphen- or dot-separated segments), then consecutive character match. Results are ranked so the best matches appear first.

---

Kind Filter — :

Prefix a resource kind with : to filter by resource type. This is one of the most frequently used filters.

:pods

Shows only Pod resources.

:deploy

Shows only Deployments.

Short names are supported — :po for pods, :deploy for deployments, :sts for statefulsets, :svc for services, and so on.

Kind stacking: The first kind selection navigates to that resource type. Each subsequent kind selection adds another kind to the view using OR logic, letting you build cross-resource views.

:pods :services

Shows both Pods and Services together in a single list.

---

Namespace Filter — @

Prefix a namespace name with @ to filter by namespace. The alias ns: also works.

@default

Shows only resources in the default namespace.

ns:kube-system

Same as @kube-system — shows only resources in the kube-system namespace.

Multi-select: Add multiple namespace filters to show resources from any of them (OR logic).

@default @kube-system

Shows resources in either the default or kube-system namespace.

Wildcard: Use @* to clear the namespace filter and show resources across all namespaces.

---

Field Filter — .

Use dot notation to filter by any field in the resource spec or status.

.status.phase=Running

Shows only resources where status.phase equals Running.

.spec.replicas=3

Shows only resources with exactly 3 replicas configured.

Operators supported:

• = — exact value match
• != — value does not match
• > / < — numeric comparison (for integer fields)

Field existence check: Omit the operator to check whether a field exists at all.

.status.phase

Shows resources that have a status.phase field, regardless of its value.

Duration comparison: Use duration syntax when comparing timestamp or age fields.

.metadata.creationTimestamp<5d

Shows resources created less than 5 days ago. Supported units: d (days), h (hours), m (minutes) — and combinations like 1h30m or 2d 23h.

Percentage comparison:

.spec.replicas>50%

Compare field values using percentages.

Autocomplete: As you type a field filter, Kunobi suggests field names, operators, and known values from the currently loaded resources.

---

Regex Filter — /

Prefix your pattern with / to use a regular expression:

/^web-.*

Shows resources whose name starts with web-.

/-(prod|staging)-

Shows resources whose name contains -prod- or -staging-.

---

Exact Match — "

Wrap a value in double quotes for an exact match (useful when the name contains special characters):

"my-service"

Shows only the resource named exactly my-service.

---

Negation — !

Prefix any filter token with ! to exclude matches instead of including them.

!@default

Excludes resources in the default namespace.

!:pods

Excludes Pod resources from the results.

!.status.phase=Running

Excludes resources whose status.phase is Running.

!"nginx-proxy"

Excludes the resource named exactly nginx-proxy.

Multiple negations work together with AND logic — each one removes an additional set of resources from the results.

---

Combining Filters

You can combine multiple filter tokens by separating them with a space. All conditions are ANDed together:

@production .status.phase=Running nginx

Shows all resources in the production namespace, with status.phase=Running, whose name matches nginx.

Kind filters integrate naturally with other filters:

:deploy @production .status.replicas>3 nginx

Shows Deployments in the production namespace with more than 3 replicas whose name contains nginx.

---

Filter Bar Features

• Filter pills — Active filters appear as removable pill badges below the input. Click the × on any pill to remove that filter.
• Autocomplete — A suggestions dropdown appears as you type, offering namespaces, kinds, field names, values, and operators relevant to your current resources.
• Match count — The filter bar shows a live filtered/total resource count so you always know how many resources match.
• Regex helper — A visual helper for constructing regex patterns with flag support (g, i, m).
• Filter history — Press ↑/↓ arrow keys in the filter input to navigate previously used filters.

---

Filter Presets

Save frequently-used filter combinations as named presets so you can apply them with a single click.

Presets capture your full filter state: active filters, column visibility, view mode, selected kinds, and namespaces. They live inside workspaces — see the Workspaces documentation for details.

Saving a Preset

1. Set up the filters you want to save using the filter bar
2. Click the Save Preset button (bookmark icon) next to the filter bar, or press ⌘S (macOS) / Ctrl+S (Windows/Linux)
3. Enter a name for the preset, or accept the auto-generated name ("Preset 1", "Preset 2", ...)
4. Click Save

Loading a Preset

1. Click the Presets dropdown next to the filter bar
2. Select a preset from the list
3. The filter bar updates instantly and the resource list is filtered

Managing Presets

• Click the edit icon next to a preset to rename it
• Click the delete icon to remove a preset
• Presets are stored locally and persist across sessions

---

Search in Discovery Sidebar

The left sidebar includes a Discovery Search to quickly jump between resource types:

1. Click the search icon at the top of the sidebar, or
2. Press ⌘K to open the command palette, then type a resource name

This is useful when you want to quickly switch from viewing Deployments to viewing Services, ConfigMaps, or any other resource type.

---

Cluster & Context Search

On the Clusters page, use the search box (⌘F) to filter clusters by context name or kubeconfig path.

---

Tips

• Filters are per-tab — each tab maintains its own independent filters. Filters set in one tab don't affect another.
• Use kind stacking (:pods :services) to create cross-resource views that show multiple resource types together.
• Use presets for filters you apply regularly (e.g., showing only Running pods in production).
• The regex filter is powerful for complex name patterns across large clusters.
• Negation (!) pairs well with broad views — show everything except what you don't need.
• Combine @* with a kind filter to quickly scan a resource type across all namespaces.