You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Headlamp cannot connect to any Kubernetes cluster (public or private) when using a local DNS resolver like dnsmasq. The connection attempts fail without any clear error messages in the UI, even though the clusters are accessible via other tools such as kubectl,openlens and dig.
Expected Outcome:
Headlamp should successfully connect to Kubernetes clusters (both public and private) when a local DNS resolver is used
To Reproduce
Steps to reproduce the bug:
Set up a local DNS resolver using dnsmasq with the following configuration:
Local private clusters mapped to IPs in dnsmasq.conf.
System configured to use 127.0.0.1 as the primary DNS resolver.
Open Headlamp.
Attempt to connect to a Kubernetes cluster (e.g., private cluster using privatelink DNS entries or public clusters).
Observe that Headlamp fails to establish a connection, even though kubectl works fine with the same kubeconfig.
Environment (please provide info about your environment):
Installation type: Mac (Homebrew)
Headlamp Version: Version 0.27.0 (0.27.0)
Other:
macOS version: 15.2
DNS setup: dnsmasq running on localhost (127.0.0.1) and configured to resolve private and public cluster domains.
Are you able to fix this issue?
No.
Additional Context
This issue occurs when dnsmasq is used as the primary DNS resolver. Without dnsmasq (using public DNS like 8.8.8.8), Headlamp works as expected.
Accessing clusters via kubectl works fine with the same kubeconfig, confirming that the issue is specific to Headlamp's DNS resolution behavior.
Regression: This might not be a regression, but earlier versions were not tested with local DNS setups.
The text was updated successfully, but these errors were encountered:
Describe the bug
Headlamp cannot connect to any Kubernetes cluster (public or private) when using a local DNS resolver like dnsmasq. The connection attempts fail without any clear error messages in the UI, even though the clusters are accessible via other tools such as kubectl,openlens and dig.
Expected Outcome:
Headlamp should successfully connect to Kubernetes clusters (both public and private) when a local DNS resolver is used
To Reproduce
Steps to reproduce the bug:
Set up a local DNS resolver using dnsmasq with the following configuration:
Local private clusters mapped to IPs in dnsmasq.conf.
System configured to use 127.0.0.1 as the primary DNS resolver.
Open Headlamp.
Attempt to connect to a Kubernetes cluster (e.g., private cluster using privatelink DNS entries or public clusters).
Observe that Headlamp fails to establish a connection, even though kubectl works fine with the same kubeconfig.
Environment (please provide info about your environment):
Installation type: Mac (Homebrew)
Headlamp Version: Version 0.27.0 (0.27.0)
Other:
macOS version: 15.2
DNS setup: dnsmasq running on localhost (127.0.0.1) and configured to resolve private and public cluster domains.
Are you able to fix this issue?
No.
Additional Context
This issue occurs when dnsmasq is used as the primary DNS resolver. Without dnsmasq (using public DNS like 8.8.8.8), Headlamp works as expected.
Accessing clusters via kubectl works fine with the same kubeconfig, confirming that the issue is specific to Headlamp's DNS resolution behavior.
Regression: This might not be a regression, but earlier versions were not tested with local DNS setups.
The text was updated successfully, but these errors were encountered: