canonical / canonical/microcloud-cluster-manager
Dynamic IP for COS stack in dev mode
Open
- Dominant language
- Go
- Stars
- 21
- Forks
- 5
- Avg merge
- 13h 56m
- Merged PRs (30d)
- 30
Description
The [dev config](https://github.com/canonical/microcloud-cluster-manager/blob/main/deployment/k8s/dev/config/dev-config.yaml#L25) hard codes the IP of Prometheus and Grafana. Sometimes another IP address is assigned on startup. The IP configuration should be dynamic depending on the current run.
Contributor guide
Research direction
Start with deployment/k8s/dev/config/dev-config.yaml around line 25, where the Prometheus and Grafana IPs are hard-coded. Run the dev configuration and inspect how IP addresses are assigned on startup. Done means the COS stack uses the current run's IP address rather than a fixed value for Prometheus and Grafana.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, grafana, kubernetes, prometheus, yaml
- Domain
- devops, infrastructure, observability
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 55/100