stackabletech / stackabletech/demos
Monitoring stack fails on installation with stackablectl
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 3
- Forks
- 13
- Avg merge
- 2d 20h
- Merged PRs (30d)
- 2
Description
Installing the monitoring stack with stackable fails when it reaches prometheus-service-monitor.yaml. Running the stack install a second time succeeds as does applying prometheus-service-monitor.yaml manually with kubectl.
manifests:
- plainYaml: demos/stacks/monitoring/grafana-dashboards.yaml
- helmChart: demos/stacks/_templates/prometheus.yaml
- plainYaml: demos/stacks/_templates/prometheus-service-monitor.yaml
This could be a race condition between the installation of the Prometheus helm chart and the creation of the ServiceMonitors.
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
Reproduce the failure with the stack install using the manifests in demos/stacks/monitoring/grafana-dashboards.yaml, demos/stacks/_templates/prometheus.yaml, and demos/stacks/_templates/prometheus-service-monitor.yaml. Compare the first installation with a second run and manual kubectl application to investigate the reported ordering issue. Done means the monitoring stack installs successfully on its first run.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, kubernetes, prometheus
- Domain
- devops, infrastructure, observability
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100