When changing the namespace, the workload remains in the old namespace
Open
Nobody has claimed this yet.
fix-on-pipedv1
kind/bug
- Dominant language
- Go
- Stars
- 1.4k
- Forks
- 364
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 84
Description
What happened:
When changing the namespace, the workload remains in the old namespace.
before
% kubectl get deployment -n test simple-hoge
NAME READY UP-TO-DATE AVAILABLE AGE
simple-hoge 2/2 2 2 12m
after
% kubectl get deployment -n test2 simple-hoge
NAME READY UP-TO-DATE AVAILABLE AGE
simple-hoge 2/2 2 2 7m8s
What you expected to happen:
It would be nice to delete the old resource successfully.
How to reproduce it:
Environment:
pipedversion:control-planeversion:- 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
Start by reproducing the namespace change described in the issue with kubectl, comparing the workload in test and test2 before and after the change. Investigate the workload reconciliation and deletion path, then verify that the old resource is deleted successfully after changing namespaces.
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