You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Detailed Description
As explained in rancher/docs#4033 (which is requesting UI documentation):
I'm using the Rancher Cluster Explorer v2.5.8 and would like to find documentation around how to filter pods with more advanced criteria (by metadata.annotations, for example). Something like "kubectl get pods -o jsonpath" with some query expression to filter on matching metadata tags.
I would like the ability to filter by more information associated with the job or pod. Right now, the "filter" search box only seems to match based on the visible data in the table.
It would be useful to be able to either add additional columns (metadata.annotations.some-tag). Alternatively, if the filter box performed a full-text search of "hidden" data about the pods such as the metadata, that could work too.
Context
Without the ability to filter the large list of jobs / pods, it makes using the Rancher UI less useful and instead I have to use kubectl with either -o jsonpath or | jq to filter on the criteria I want.
The text was updated successfully, but these errors were encountered:
Detailed Description
As explained in rancher/docs#4033 (which is requesting UI documentation):
I would like the ability to filter by more information associated with the job or pod. Right now, the "filter" search box only seems to match based on the visible data in the table.
It would be useful to be able to either add additional columns (metadata.annotations.some-tag). Alternatively, if the filter box performed a full-text search of "hidden" data about the pods such as the metadata, that could work too.
Context
Without the ability to filter the large list of jobs / pods, it makes using the Rancher UI less useful and instead I have to use kubectl with either
-o jsonpath
or| jq
to filter on the criteria I want.The text was updated successfully, but these errors were encountered: