stackhpc / stackhpc/azimuth-llm
Huggingface won't install on clusters with the Monitoring addon disabled
Nobody has claimed this yet.
- Dominant language
- Jupyter Notebook
- Stars
- 9
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
azimuth-chat (HuggingFace LLM Kubernetes app) gives Error: unable to build kubernetes objects from release manifest: resource mapping not found for name: "test-llm-no-monit" namespace: "" from "": no matches for kind "ServiceMonitor" in version "[monitoring.coreos.com/v1](http://monitoring.coreos.com/v1)" ensure CRDs are installed first when trying to install on clusters with the Cluster Monitoring cluster addon disabled.
Can this be solved without disabling the ServiceMonitor altogether; i.e. by detecting if the Monitoring cluster addon is enabled first and setting .Values.api.monitoring.enabled?
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 with the azimuth-chat Helm chart and the ServiceMonitor configuration controlled by .Values.api.monitoring.enabled. Check how the chart handles clusters without the Cluster Monitoring addon, then verify that installation no longer renders a ServiceMonitor when the addon is disabled while retaining it when enabled.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- helm, huggingface, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 42/100