HTTPRoute Details and AND Filtering

[sule26]

Hello again! Sorry to bother you once again!

Hostnames and Route views

Whenever I try to look at my HTTPRoutes, I can't see every hostname and route that the HTTPRoute itself is configured for.

I wish I could see every hostname and every route configured for the HTTPRoute.

AND Operator in filters

We talked earlier about allowing users to use |, like in istiod|istio-cni-node, to filter multiple things at once. However, I believe being able to use an AND operator with & or && would also be very useful.

For example, something like team-a&arm64 would allow me to filter nodes that belong to team-a and have the arm64 architecture.

This would be especially useful when I want to filter nodes based on multiple properties at the same time.

[nklmilojevic]

Thanks for the report. I checked the current code for HTTPRoute views.

The built-in view includes all hostnames, joined with commas. Your screenshot also shows a ROUTE column, which is not part of the built-in view. This suggests that a custom view may be in use.

A custom path such as /spec/hostnames/0 selects only the first hostname. A path such as /spec/rules/0/matches/0/path/value selects only the first path. Custom column paths use JSON Pointer and do not expand * across arrays.

Could you share your sofka version and the HTTPRoute section of your view configuration? Please remove any private values. This will help confirm whether the missing values come from the configuration or the display.

If a custom HOSTNAMES column selects only the first item, removing that override restores the built-in list. Setting its path to /spec/hostnames also shows the full array as JSON. There is currently no built-in column that collects all route matches. The YAML view (y) shows the full object, but a readable route summary would need additional work.

For AND filtering, the current code supports both team-a arm64 and team-a && arm64. These search names, namespaces, and displayed columns. To search labels that are not displayed, use label:team-a && label:arm64. Your version will help us check whether these options are available in your installation.

[sule26]

Yeah, my custom view was the issue. I just fixed the hostname config by replacing /spec/hostnames/0 with /spec/hostnames/. For routes, it is as you said: /spec/rules/0/matches/0/path/value.

That being said, being able to see every route would be very useful. At my company, we have a lot of APIs exposed using the same hostname, so being able to see all the routes at once would make life much easier.

[views."gateway.networking.k8s.io/v1/httproutes"]
columns = [
  { name = "HOSTNAMES", path = "/spec/hostnames/" },
  { name = "ROUTE",     path = "/spec/rules/0/matches/0/path/value" },
]

I did not know that about AND filtering. Thanks!

[nklmilojevic]

Thanks for confirming the cause. We will add a built-in ROUTES column that collects paths from all rules and matches, includes the match type, and removes duplicate entries. Matches without an explicit path will show Prefix /. The column will use the existing table width limits; the YAML view will still show the full object.

One correction to the configuration: use /spec/hostnames without the final slash to select the full array. The current code uses JSON Pointer directly.

I will track the ROUTES column in an issue. General wildcard support for custom columns is outside this scope.

[sule26]

I'll be looking forward to it. Thanks again!

[nklmilojevic]

Tracked in #733. The hostname configuration and AND filtering questions are resolved. I am closing this discussion; implementation will continue in the issue.

[sule26]

Wouldn't be a better ideia to use /* when its pathPrefix and Exact only show de path?

Example:
pathPrefix: /api/*
Exact: /api