Skip to main content
Kubewall provides multiple search and filtering mechanisms to help you quickly find resources in clusters of any size, from small development environments to large production clusters with thousands of resources.

​
Overview

The filtering system operates at multiple levels to help you narrow down resources efficiently:

Global Search

Search across all visible columns in resource tables

Namespace Filter

Filter resources by one or more namespaces

Faceted Filters

Multi-select filters for specific columns

Command Palette

Quick navigation to any resource type (Cmd/Ctrl+K)
The global search box appears in the toolbar of every resource list:

​
How to Use

  1. Type in the search box at the top of the resource list
  2. Results filter instantly as you type
  3. Searches across all visible columns
  4. Case-insensitive fuzzy matching

​
What Gets Searched

The search indexes these fields for all resources:
  • Name: Resource name
  • Namespace: Resource namespace (if namespaced)
  • Labels: All label key-value pairs
  • Annotations: Annotation keys (not values)
  • Status: Current status or phase
  • Age: Created timestamp

​
Search Examples

nginx           → Find resources with "nginx" in name or labels
production      → Find resources in production namespace or with production label
8080            → Find services or pods using port 8080
crashloot       → Find pods in CrashLoopBackOff (fuzzy match)
app=frontend    → Find resources with that label
192.168         → Find pods with matching IPs
The fuzzy matching is forgiving - slight typos still return results.

​
Search Tips

  • Start typing immediately: Search activates as soon as you type
  • Clear with X: Click the X icon to clear the search
  • Combine with filters: Use global search + namespace filter together
  • Search persists: Search string maintained as you navigate resource types
Global search operates on the client side, filtering results already loaded in your browser. This makes it extremely fast.

​
Namespace Filtering

The namespace filter helps you focus on specific namespaces:

​
Using the Namespace Filter

  1. Click the Namespace dropdown in the toolbar
  2. Select one or more namespaces
  3. Table updates to show only resources in selected namespaces
  4. Selected namespaces show with a checkmark
  5. Click again to deselect
Select one namespace to view only resources in that namespace:
  • Useful for focusing on a specific application
  • Reduces noise from other namespaces
  • Common for development/staging/production separation
  • Great for troubleshooting namespace-specific issues

​
Namespace Filter Behavior

  • Persists: Selection maintained as you navigate resource types
  • Cluster-Scoped Resources: Filter disabled for Nodes, PVs, ClusterRoles
  • Custom Resources: Namespace filter works on namespaced CRs
  • Clear Filter: Deselect all to return to all-namespace view
Namespaces in the dropdown are organized:
  • System Namespaces: kube-system, kube-public, kube-node-lease (grouped)
  • Application Namespaces: Your custom namespaces (alphabetical)
  • Current Selection: Checked namespaces appear at top
  • Empty Namespaces: Shown even if no resources of current type

​
Faceted Filters

Faceted filters provide column-specific filtering with multi-select:

​
Available Faceted Filters

Depends on the resource type and visible columns:

Status

Filter by pod phase, deployment status, etc.

Labels

Filter by specific label keys and values

Node

Filter pods by the node they’re running on

Type

Filter services by type (ClusterIP, NodePort, LoadBalancer)

​
Using Faceted Filters

  1. Click the filter icon next to a column header
  2. Select one or more values from the dropdown
  3. Table filters to show only matching rows
  4. Multiple selections use OR logic (show any match)
  5. Multiple filters use AND logic (must match all)
Faceted filters are particularly useful for status columns - quickly show only Running pods, or only Failed pods.

​
Example Filter Combinations

Find failing pods in production:
  1. Namespace Filter: Select production
  2. Status Filter: Select Failed, CrashLoopBackOff
  3. Result: Only problematic pods in production

​
Command Palette

The command palette provides instant navigation to any resource type:

​
Opening the Palette

  • Keyboard: Press Cmd+K (Mac) or Ctrl+K (Windows/Linux)
  • Click: Click the search button in the sidebar

​
Using the Palette

  1. Type to search for resource types
  2. Matches appear instantly
  3. Use arrow keys to navigate results
  4. Press Enter to navigate to selected resource
  5. Press Escape to close without navigating
  • Fuzzy Search: Type partial names (e.g., “deploy” matches “Deployments”)
  • Category Grouping: Resources grouped by category (Workloads, Network, etc.)
  • Custom Resources: Includes all CRDs in your cluster
  • Keyboard Navigation: Fully keyboard-accessible
  • Recently Used: (future enhancement)

​
Example Searches

dep         → Deployments
ser         → Services
pod         → Pods
sec         → Secrets
conf        → ConfigMaps
crds        → Custom Resource Definitions

​
Column Visibility

Customize which columns appear in resource tables:

​
Managing Columns

  1. Click the View Options button (columns icon) in toolbar
  2. Check/uncheck columns to show/hide
  3. Table updates immediately
  4. Preferences persist in browser session
Hiding unused columns makes tables easier to scan and improves performance with large resource lists.

​
Default Visible Columns

  • Name
  • Namespace
  • Status
  • Ready (containers)
  • Restarts
  • Age
  • IP
  • Node

​
Table Sorting

Click any column header to sort the table:
  • First Click: Sort ascending
  • Second Click: Sort descending
  • Third Click: Remove sort (return to default)

​
Sortable Columns

  • Name: Alphabetical
  • Namespace: Alphabetical
  • Age: Chronological (newest/oldest)
  • Status: Alphabetical
  • Replicas: Numerical
  • Restarts: Numerical
Sorting is client-side and instant, even with thousands of resources.

​
Multi-Select for Bulk Actions

Select multiple resources for bulk operations:

​
Selection Methods

  1. Individual: Click checkbox on any row
  2. All: Click checkbox in header to select all visible rows
  3. Range: (future enhancement - Shift+Click)

​
Bulk Actions

  • Delete: Delete all selected resources
  • Export: (future enhancement)
  • Label: (future enhancement)
Bulk delete is permanent. Review your selection carefully before confirming.

​
Search Performance

​
Client-Side Filtering

All search and filtering operates on the client side: Advantages:
  • Instant results as you type
  • No network latency
  • Works with real-time updates
  • Smooth user experience
Considerations:
  • Entire resource list must load first
  • Very large clusters (10,000+ resources) may be slower
  • Use namespace filter to reduce data set
For Large Clusters:
  1. Filter by namespace first to reduce data
  2. Use specific resource types (not “All Resources”)
  3. Hide unused columns to speed rendering
  4. Use global search to reduce visible rows
  5. Consider RBAC to limit accessible resources

​
Advanced Filtering Techniques

While Kubewall doesn’t support label selector syntax directly, you can:
  1. Use global search for label values
  2. Type app=frontend to find matching resources
  3. Combine with namespace filter for precision
  4. Use faceted filter for specific label keys

​
Best Practices

Use Namespaces

Organize resources into namespaces for easier filtering

Consistent Labels

Apply consistent labels to make faceted filtering effective

Meaningful Names

Use descriptive resource names that are easy to search

Clear Filters

Clear filters when switching contexts to avoid confusion

​
Keyboard Shortcuts

ShortcutAction
Cmd/Ctrl+KOpen command palette
EscapeClose command palette
↓ ↑Navigate command palette results
EnterSelect from command palette
TabNavigate between filters

​
Next Steps

Resource Management

Learn how to manage filtered resources

Real-Time Monitoring

Understand real-time updates in filtered views

Build docs developers (and LLMs) love

Get started for freeTalk to us