cockroachdb / cockroachdb/cockroach-operator
Improve Version Checker Job Pending Edge Case
Open
- Dominant language
- Go
- Stars
- 318
- Forks
- 104
- Avg merge
- 1d 6h
- Merged PRs (30d)
- 1
Description
When the Job does not schedule we are starting a new Job. We need to determine what the edge case behavior needs to be. At this point, we just start a new job every two minutes.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by tracing the Version Checker Job scheduling path and how a pending Job is detected. Determine the intended behavior for an unscheduled Job before changing the current two-minute restart behavior. Done means the pending edge case has an agreed outcome and is covered by tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100