temporalio / temporalio/temporal-worker-controller
run-book candidate: Steps an operator should take on pod initialization errors
Open
Nobody has claimed this yet.
documentation
- Dominant language
- Go
- Stars
- 187
- Forks
- 70
- Avg merge
- 4d 1h
- Merged PRs (30d)
- 31
Description
- The controller logs don't show if there have been errors on pod initialization. One such error can simply be that the container is referencing an invalid docker image. Since the controller doesn't output these errors as logs (and it shouldn't), the operator should
kubectl describethe erroring out pod and fix such errors.
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
No file or test is named. Start by locating the project's operator run-book or documentation for pod initialization, then document that these errors are not exposed in controller logs and that operators should use kubectl describe on the failing pod, including invalid Docker images as an example. Done when the operator steps are documented clearly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- docker, kubernetes
- Domain
- devops, documentation
- Issue type
- Documentation
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 50/100