cluster.local appears in domain name
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 35/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- helm, kubernetes
- Domain
- devops, infrastructure
Research direction
Start with charts/devlake/templates/deployments.yaml and inspect the hardcoded service URLs containing cluster.local, along with the chart values that configure service discovery. Confirm the chart can use the cluster's configured domain and verify the DevLake UI no longer receives a 502 when resolving the lake and Grafana services.
Written by the indexing model from the issue text.
Description
Hello Team,
After installing DevLake I receive 502 error.
Inspecting the UI pod logs, I see records like this:
2025/09/18 07:50:32 [error] 23#23: *87 devlake-lake.ep-devlake.svc.cluster.local could not be resolved (3: Host not found)...
Inspecting the pod, I see proper records at the resolv.conf:
search ep-devlake.svc.k8s-msq-sbx svc.k8s-msq-sbx k8s-msq-sbx exadel.by
nameserver 169.254.25.10
options ndots:5
After manual edit of the devlake-ui deployment replacing 'cluster.local' with proper 'k8s-msq-sbx' it starts working properly.
I've checked the helm chart and it seems to be hardcoded to me:
% grep -r cluster.local charts/devlake/templates/deployments.yaml: value: {{ include "devlake.fullname" . }}-lake.{{ .Release.Namespace }}.svc.cluster.local:8080 charts/devlake/templates/deployments.yaml: value: {{ .Release.Name }}-grafana.{{ .Release.Namespace }}.svc.cluster.local:80
Could you please tell if it's possible use the proper domain?
- Dominant language
- Go Template
- Stars
- 52
- Forks
- 71
- Avg merge
- 16h 15m
- Merged PRs (30d)
- 1
Getting set up
This project ships no dev container, Dockerfile or contributing guide, so setting up is up to you: start from its README, and see our first-contribution guide for the general steps.
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from apache/devlake-helm-chart
-
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
apache/devlake-helm-chart#367 · 6 comments · 2 reactions ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
apache/devlake-helm-chart#366 · 1 comment ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/devlake-helm-chart#381 ·
-
Difficulty 4/5 3-5 days Newbie friendliness 48/100
apache/devlake-helm-chart#374 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 35/100
apache/devlake-helm-chart#373 · 1 comment ·
All issues in apache/devlake-helm-chart
Similar issues
-
Difficulty 1/5 1-3 hours Newbie friendliness 88/100
-
backend tests
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
lognorman20/monaco#2223 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
community-scripts/ProxmoxVE#17674 ·
Maintainers usually reply within 1 day
-
incomplete
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
opnsense/plugins#5763 · 1 comment ·
Maintainers usually reply within 1 day