Fix: return all http routes of a namespace (k8s)

[arthur-leclerc]

Proposed change

The Kubernetes integration was only returning a single HTTPRoute per namespace due to array destructuring in the listHttpRoute function. This limited the service discovery capabilities for users with multiple HTTPRoutes in the same namespace.

I don't quite understand why it was limited to one HTTPRoute per namespace, as it's certainly interesting to have multiple HTTPRoute in the same namespace, on one or more Gateway, and thus exposing multiple services on the Homepage. As a result, I have flagged this as a bug.

Closes # (issue)

Type of change

• New service widget
• Bug fix (non-breaking change which fixes an issue)
• New feature or enhancement (non-breaking change which adds functionality)
• Documentation only
• Other (please explain)

Checklist:

• If applicable, I have added corresponding documentation changes.
• If applicable, I have reviewed the feature / enhancement and / or service widget guidelines.
• I have checked that all code style checks pass using pre-commit hooks and linting checks.
• If applicable, I have tested my code for new features & regressions on both mobile & desktop devices, using the latest version of major browsers.

[shamoon]

@djeinstine @dudo any thoughts here?

[dudo]

Hello, Arthur! There are some assumptions made within the helpers about the first route. I think it's fair to assume that the schema will be the same for all routes within a resource. Good change!

[shamoon]

Thanks to you both