kubernetes drift detector can not detect changes when annotations were deleted
Open
Nobody has claimed this yet.
kind/bug
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
kubernetes drift detector can not detect the change when labels that are put by piped are deleted
What you expected to happen:
How to reproduce it:
Environment:
pipedversion: 0.42.1control-planeversion: 0.42.1- Others:
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
No files, tests, or entry points are mentioned. Start by locating the Kubernetes drift detector and reproduce deletion of labels or annotations added by piped; done means the detector reports those deletions as drift.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- devops, infrastructure
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100