1. Proposed title of this feature request
-> Persistent customizable pod filters in OpenShift Console UI

2. What is the nature and description of the request?

The filter setting on the "/pods"-view should be persisted per user, just as it's already implemented for the Manage-columns feature.
It could be implemented in the same manner as the "Manage-columns" -feature where a change in the selected columns for display results in a
PATCH-request to
.../api/kubernetes/api/v1/namespaces/openshift-console-user-settings/configmaps/user-settings-04204de0-a794-4f73-ac2b-eaa5cf1ca09c
with payload:
{"data":{"console.tableColumns":"

{\"core~v1~Pod\":[\"name\",\"namespace\",\"status\",\"ready\",\"owner\",\"created\",\"node\",\"labels\"]}

"}}

The user settings for "console.tableColumns" are persisted and read back every time the same user accesses the "/pods"-view.
The same approach could be used for a new data-set for "consolePodStatusFilter".

3. Why do you need this? (List the business requirements here)

It is overwhelming to always see a huge list of pods in various states on a project. Depending on the use-case you want to see running pods only or when trouble-shooting see only failed pods. The possibility of filtering is a great help here, but the filter-setting should be persisted, just like it's already implemented for the displayed columns (manage-columns feature).

4. List any affected packages or components.
-> OpenShift WebConsole