mayadata-io / mayadata-io/d-operators
feat: assert pod restart count
Open
Nobody has claimed this yet.
assert
enhancement
pod
recipe
use case
- 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 pod restart count to be 0 or within a configured value. I want Recipe custom resource to provide me an option to assert this.
containerStatuses:
- containerID: docker://8b659952c5a3a8dc2834192073a2bd080a12b3fed1719d980ba44d5c1f8a76b2
image: k8s.gcr.io/etcd:3.4.3-0
imageID: docker-pullable://k8s.gcr.io/etcd@sha256:4afb99b4690b418ffc2ceb67e1a17376457e441c1f09ab55447f0aaf992fa646
lastState:
terminated:
containerID: docker://1fa42f9735933cd91b2785a96538083cafc84372177b2e9e7632161b1ef3c3a9
exitCode: 255
finishedAt: "2020-05-28T06:52:19Z"
reason: Error
startedAt: "2020-05-15T16:20:29Z"
name: etcd
ready: true
restartCount: 2
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 by locating the Recipe custom resource definition and the controller entry point that evaluates pod status. Trace how existing assertions are configured and checked, then verify that a configured restart-count limit is enforced for container statuses. Done means a Recipe can assert restart count equals zero or stays within a configured value.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100