mayadata-io / mayadata-io/d-operators
use case: add experiment(s) to assert kubernetes apiservices
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 10
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
ProblemStatement: As an automation engineer, I want to assert if all kubernetes apiservices are running. In addition, I want to get the errors / issues for those apiservices that are not in running state.
refer: kubectl get apiservices
refer: https://github.com/mayadata-io/oep/issues/220
debug message from a failed apiservice:
failing or missing response from https://10.43.124.28:443/apis/metrics.k8s.io/v1beta1:
Get https://10.43.124.28:443/apis/metrics.k8s.io/v1beta1:
dial tcp 10.43.124.28:443: connect: no route to host
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
Start with the referenced kubectl get apiservices output and the linked mayadata-io/oep issue, then inspect how experiments are organized in d-operators. Done means checking every Kubernetes APIService for a running state and reporting the relevant failure or connectivity error for each one that is not running.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- api, testing-qa
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100