v2.0.0 Kubernetes integration broken on IPv6-only kubernetes Service (worked in v1.13.2)

[fmurodov]

Description

Upgraded from v1.13.2 to v2.0.0 and lost all Kubernetes service discovery plus the
cluster/node widgets. Nothing gets discovered anymore and the logs just repeat
"NaN undefined undefined" for every resource type.

My cluster is IPv6-only, so the default kubernetes Service is IPv6 and the pod gets
KUBERNETES_SERVICE_HOST=fd00::1 with no brackets. Looks like v2 builds the API URL as
https://: without bracketing the IPv6 address, so it ends up hitting
https://fd00::1:443 which isn't a valid URL. That's why the status is NaN instead of a
real 401/403 — the request never actually goes out. v1.13.2 didn't have this problem.

Running on Kubernetes with plain manifests, kubernetes.yaml uses mode: cluster.

homepage version

v2.0.0

Installation method

Other (please describe above)

Configuration

# kubernetes.yaml
mode: cluster
gateway: true

# kubernetes Service is IPv6-only, so the pod gets KUBERNETES_SERVICE_HOST=fd00::1 (no brackets)

Container Logs

error: Error getting pods: NaN undefined undefined
error: Error getting httproutes: NaN undefined undefined
error: Error getting ingresses: NaN undefined undefined
error: Error getting nodes: NaN undefined undefined

Browser Logs

n/a, it's all server side

Troubleshooting

RBAC and the token are fine (can-i list pods/nodes/httproutes all return yes), so it's
not permissions. Tested from inside the pod and only the unbracketed form breaks:

  wget https://fd00::1:443/api                            -> hangs/fails
  wget https://[fd00::1]:443/api                          -> 200
  wget https://kubernetes.default.svc.cluster.local/api   -> 200

Working around it by pointing at the DNS name instead:

  env:
    - name: KUBERNETES_SERVICE_HOST
      value: kubernetes.default.svc.cluster.local
    - name: KUBERNETES_SERVICE_PORT
      value: "443"

Did that in my own repo and it fixed it: fmurodov/homeops#746
Probably wants an actual fix that brackets IPv6 hosts though.

[shamoon]

Hmm, I wonder if its related to the underlying package, I'll look into it later thanks

[shamoon]

I think this has been nodejs/node#64032 all along

Hmm

[shamoon]

Would you be able to please re-test :dev (make sure to re-pull of course)

[michaelbeaumont]

it works!

[shamoon]

Sweet, yea that confirms its the node issue.

Thanks, I should be able to drop 2.1.1 today with this.

[michaelbeaumont]

Nice one, incredible it's been unfixed in node itself for 2 months 🤯

[shamoon]

It's fixed in node 26 (which isnt LTS yet). I think it will eventually be back-ported and released, though I dont know how far. homepage is still on 22

Yea annoying but this should do it and I'll keep an eye out for when its back ported and we'll probably update node version in the container soon anyway

[github-actions[bot]]

This discussion has been automatically closed because it was marked as answered. See our contributing guidelines for more details.

[fmurodov]

Just upgraded to 2.1.2 and it works.
Thanks @shamoon