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
What problem are you trying to solve? Do you a suggestion on how to solve it?
Current Behavior:
When searching for nodes with a specific taint (e.g., nodeType:monitoring) in the cluster, the current search functionality appears to be limited to node names or other straightforward identifiers. This limitation becomes evident when using tools like Aptakube or OpenLens, where, for example, a search in Aptakube yields no results, whereas OpenLens might return two nodes without explicitly considering the taint key/value pairs.
In aptakube
In OpenLens
Suggested Enhancement:
I propose the addition of a node search filter that allows users to query based on the key/value pairs of taints. This enhancement would significantly improve the user experience by providing a more granular and targeted search capability, especially in environments with complex taint and toleration setups.
The text was updated successfully, but these errors were encountered:
What problem are you trying to solve? Do you a suggestion on how to solve it?
Current Behavior:
When searching for nodes with a specific taint (e.g., nodeType:monitoring) in the cluster, the current search functionality appears to be limited to node names or other straightforward identifiers. This limitation becomes evident when using tools like Aptakube or OpenLens, where, for example, a search in Aptakube yields no results, whereas OpenLens might return two nodes without explicitly considering the taint key/value pairs.
Suggested Enhancement:
I propose the addition of a node search filter that allows users to query based on the key/value pairs of taints. This enhancement would significantly improve the user experience by providing a more granular and targeted search capability, especially in environments with complex taint and toleration setups.
The text was updated successfully, but these errors were encountered: