K8s monitor deploy should keep the same dns with image
Open
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 29
- Forks
- 46
- Avg merge
- 12h 51m
- Merged PRs (30d)
- 17
Description
For now, the dns of k8s-monitor yaml is http://prometheus-k8s.monitoring.svc, but in our image, we use http://k8s-prometheus.monitoring.svc
Contributor guide
No contributing guide indexed for this repository
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.
Research direction
Start by locating the k8s-monitor YAML and the image configuration that defines its Prometheus DNS. Compare the two service names and update the deployment configuration so both use the same DNS, then verify the rendered Kubernetes configuration contains the consistent endpoint.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100