pulp-operator just removed my whole development namespace.
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 88
- Forks
- 66
- Avg merge
- 53m
- Merged PRs (30d)
- 1
Description
Version
2.0
Describe the bug
I tried to deploy in our development namespace and then I did an undeploy. This resulted in my whole development namespace was removed with like 20 developers getting stopped.
To Reproduce
make undeploy
Expected behavior
I expected it to only remove its own resources, not the whole namespace. The documentation does not mention this. I just suggest setting NAMESPACE
Additional context
This is a really critical error I would say.
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 with the make undeploy target and trace how NAMESPACE is selected and passed to the operator resources. Verify the undeploy path against a shared development namespace, then ensure the documented configuration makes it remove only Pulp resources without deleting the namespace.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go, kubernetes
- Domain
- infrastructure
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100