NVIDIA / NVIDIA/ai-cloud-validation
K8sApiServerMetricsCheck: metric names are matched but labels are not, so SLO calculability is unproven
Open
Beginner friendly
Nobody has claimed this yet.
bug
kubernetes
priority-2
- Dominant language
- Python
- Stars
- 27
- Forks
- 33
- Avg merge
- 1d 15h
- Merged PRs (30d)
- 28
Description
The test verifies we can retrieve API server metrics, but it doesn’t check the actual labels of the Prometheus-style metric to make sure we can calculate SLO - can improve test depth
Contributor guide
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
Locate the K8sApiServerMetricsCheck test entry point and inspect the existing assertion that verifies metric names. Determine which Prometheus metric labels are required for SLO calculation, add coverage for them, and run the relevant Python tests to confirm the labels are validated.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- kubernetes, prometheus, python
- Domain
- observability, testing
- Issue type
- Bug
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Active
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100