constructedServiceFromResource crashes on HTTPRoute without parentRefs (TypeError: ... reading '0')

[zewelor]

Description

I encountered a crash in the service discovery process when using an HTTPRoute resource that does not have parentRefs defined. The logs show a TypeError: Cannot read properties of undefined (reading '0').

Configuration:
Gateway API discovery is enabled in kubernetes.yaml:

mode: cluster
gateway: true # enable Kubernetes Gateway API (HTTPRoute) discovery

Root Cause Analysis:
I believe the issue is located in src/utils/kubernetes/resource-helpers.js within the getUrlFromHttpRoute function.
The code assumes that if hostnames are present on an HTTPRoute, parentRefs must also be present and populated. It attempts to access resource.spec.parentRefs[0] directly to determine the URL schema (http/https).

https://github.com/gethomepage/homepage/blob/main/src/utils/kubernetes/resource-helpers.js#L51

// src/utils/kubernetes/resource-helpers.js

async function getUrlFromHttpRoute(resource) {
  let url = null;
  const hasHostName = resource.spec?.hostnames;

  if (hasHostName) {
    if (resource.spec.rules[0].matches[0].path.type !== "RegularExpression") {
      const urlHost = resource.spec.hostnames[0];
      const urlPath = resource.spec.rules[0].matches[0].path.value;
      // CRASH HERE: parentRefs is undefined if omitted from the spec
      const urlSchema = await getSchemaFromGateway(resource.spec.parentRefs[0]);
      url = `${urlSchema}://${urlHost}${urlPath}`;
    }
  }

  return url;
}

Steps to Reproduce:

1. Enable gateway: true in config/kubernetes.yaml.
2. Define an HTTPRoute resource in Kubernetes that has hostnames but no parentRefs. This is a valid configuration when using mechanisms like "Default Gateways".
3. Homepage attempts to discover services.
4. The application throws TypeError: Cannot read properties of undefined (reading '0') and fails to discover services.

Expected Behavior:
Homepage should correctly handle HTTPRoute resources where parentRefs is not explicitly defined, as this is a valid configuration according to the Gateway API specification.

References:
For more context on why parentRefs can be omitted (e.g. "Default Gateways"), see:
https://kubernetes.io/blog/2025/11/06/gateway-api-v1-4/#introducing-default-gateways

homepage version

1.9.0

Installation method

Docker

Configuration

kubernetes.yaml:

mode: cluster
gateway: true # enable Kubernetes Gateway API (HTTPRoute) discovery

Container Logs

[2026-01-23T18:32:01.713Z] error: TypeError: Cannot read properties of undefined (reading '0')
at k (/app/.next/server/chunks/7655.js:1:17544)
at l (/app/.next/server/chunks/7655.js:1:17625)
at Object.n [as constructedServiceFromResource] (/app/.next/server/chunks/7655.js:1:18173)
at /app/.next/server/chunks/7655.js:1:12360
at Array.map ()
at t (/app/.next/server/chunks/7655.js:1:12343)
at process.processTicksAndRejections (node:internal/process/task_queues:105:5)
at async q (/app/.next/server/pages/api/bookmarks.js:1:2946)
at async g (/app/.next/server/pages/api/services.js:1:185)
[2026-01-23T18:32:01.714Z] error: Failed to discover services, please check kubernetes.yaml for errors or remove example entries.

Browser Logs

No response

Troubleshooting

• Checked container logs and identified the stack trace pointing to constructedServiceFromResource.
• Reviewed the source code in src/utils/kubernetes/resource-helpers.js.
• Confirmed that getUrlFromHttpRoute attempts to access resource.spec.parentRefs[0] without checking if parentRefs is defined.
• Verified that the error correlates with deploying an HTTPRoute resource that omits the parentRefs field (relying on Default Gateways).

[shamoon]

Once again proving k8s is unwieldy. If they added support for this in November I would just see it as a breaking change for homepage. Happy to accept a PR for it, I don’t use k8s so it’s not a high priority thing for me.

Since literally everything is AI right now and it might be killing FOSS I would only ask that a PR (AI or not) be careful about not breaking things for existing users

[github-actions[bot]]

This discussion has been automatically closed due to inactivity. See our contributing guidelines for more details.

[github-actions[bot]]

This discussion has been automatically locked since there has not been any recent activity after it was closed. Please open a new discussion for related concerns. See our contributing guidelines for more details.