Deployment lifecycle hooks should have ownerRef to deployer pod
Open
Nobody has claimed this yet.
area/reliability
component/apps
lifecycle/frozen
lifecycle/stale
priority/P2
- Dominant language
- Go
- Stars
- 8.7k
- Forks
- 4.8k
- Avg merge
- 4d 10h
- Merged PRs (30d)
- 53
Description
When you delete the running deployer pod, the pre/post hook will keep running forever. The lifecycle hook pods should have ownerRef set to the deployer pod and be tied to the lifecycle of the deployer pod (as that pod controls them).
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 files, tests, or entry points are named. Start by locating where deployment lifecycle hook pods are created and owner references are assigned; verify that deleting the deployer pod also cleans up its pre- and post-hook pods.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- ci-cd, devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100