Repository navigation
Dashboard 1.4.0 lacks of detailed information about services #2789
Description
Describe the bug
Earlier (before 1.4.0) Cozystack users could obtain all necessary information about provisioned services from the dashboard, including external IP (assigned by MetalLB to kubernetes services of type LoadBalancer) and FQDN (which was handy too if coredns was tuned to expose these external IPs via a separate zone).
Now in 1.4.x the Dashboard neither displays LoadBalancer IPs, nor FQDN to be used to connect to the provisioned services.
Environment
- Cozystack version: 1.4.2 (looks like dashboard update wasn't a part of release 1.4.2, so it keeps displaying 1.4.1)
- Provider: on-prem
To Reproduce
Steps to reproduce the behavior:
- Upgrade or install CozyStack 1.4.2 with MetalLB and configure a pool for LoadBalancer IPs
- Provision any service, e.g. redis with external flag set to true.
- Go to its details and services tab.
- See that there is no information how to connect to it.
Expected behaviour
Services tab should either display the LoadBalancer IP, or both the LoadBalancer IP and the FQDN of the service (preferably with a configurable domain suffix, like it used to be in pre-1.4.0 versions, where it could be configured via patching the kube-service-details factory)
Actual behaviour
Lack of critically important details about the provisioned services.
Logs
N/A
Checklist
- I have checked the documentation
- I have searched for similar issues
- I have included all required information
- I have provided clear steps to reproduce
- I have included relevant logs

Activity
lexfrei commentedon Jun 3, 2026
Confirmed — this is a real regression in the 1.4.x dashboard, not a misconfiguration on your side.
Root cause: the app detail → Services tab (
ServicesTab.tsxin cozystack-ui) lists Services reading onlyspec(type / clusterIP / ports); it never readsstatus.loadBalancer.ingress[].ip, so the MetalLB-assigned external IP isn't shown. The data is available and already used elsewhere — Administration → External IPs reads exactly that field per tenant, which works as a stopgap today.The FQDN part is a separate gap: the new UI has no equivalent of the old kube-service-details factory with a configurable domain suffix, so showing a connection FQDN is a feature that needs a domain-source decision, not just wiring.
Tracking the fix in the dashboard repo:
Leaving this open as the user-facing umbrella. Thanks for the detailed report and screenshot.
fix(dashboard): show LoadBalancer external IP on the app Services tab (…
fix(dashboard): show LoadBalancer external IP on the app Services tab