Is your feature request related to a problem? Please describe the impact that the lack of the feature requested is creating.

ClusterTable does not persist filter, sorting and column settings between page reloads. For users who change clusters in AWS often (and spin up and down new clusters regularly), this results in a lot of time re-filtering, sorting and updating columns. Example images included in the additional context section.

Describe the solution you'd like

Following the design found in ResourceTable to store the state of the ClusterTable's filter, sort and column settings so that interactions with ClusterTable persist for the session.

What users will benefit from this feature?

Cloud users that manage many Kubernetes clusters, especially clusters that are deployed and destroyed regularly. Especially those in AWS where clusters are listed as the full arn and may not be entirely visible on table load.

Are you able to implement this feature?

Yes (I will propose a PR)

Additional context

Reset view on every load of the cluster page, long AWS cluster names result in a required action of re-updating filter, sort and column each time:

Sorted and updated Columns for easy switching when table settings are persisted in local storage: