pulp-operator just removed my whole development namespace.
Maintainers usually reply within 4 days
Nobody has claimed this yet.
Assessment
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Newbie friendliness
- 45/100
- Issue type
- Bug
- Clarity
- Mostly clear
- Activity status
- Quiet
- Tech stack
- go, kubernetes
- Domain
- infrastructure
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.
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.
- Dominant language
- Go
- Stars
- 88
- Forks
- 68
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 1
Getting set up
- Ships a Dockerfile or Docker Compose file
- Has a pull request template
- Read the contributing 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.
More from pulp/pulp-operator
-
settings.py flaps between reconciles: needsMigrationSetting depends on map iteration orderPossibly taken @fontaineajulien claimed this 4 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
pulp/pulp-operator#1691 ·
Maintainers usually reply within 4 days
-
Documentation for metadata signing (APT/RPM) removed but still relevantMay be free again A pull request for this issue was closed without being merged. OpenIssue Triage-Needed
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
pulp/pulp-operator#1644 ·
Maintainers usually reply within 4 days
-
Issue Triage-Needed
Difficulty 3/5 1-2 days Newbie friendliness 74/100
pulp/pulp-operator#1685 ·
Maintainers usually reply within 4 days
-
Feature Triage-Needed
Difficulty 5/5 Over a week Newbie friendliness 35/100
pulp/pulp-operator#1682 ·
Maintainers usually reply within 4 days
-
Job definition for reset-admin-password doesn't propagate image pull policyMay be free again A pull request for this issue was closed without being merged. OpenIssue
Difficulty 2/5 1-3 hours Newbie friendliness 55/100
pulp/pulp-operator#1630 ·
Maintainers usually reply within 4 days
All issues in pulp/pulp-operator
Similar issues
-
Difficulty 1/5 Under an hour Newbie friendliness 88/100
Maintainers usually reply within 1 day
-
agent-research agent-review-finding chore
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
jordansmall/spindrift#4922 ·
Maintainers usually reply within 1 day
-
gcsartifact: deleting a missing version returns an errorPossibly taken @ktsoator claimed this today. Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
Maintainers usually reply within 2 days
-
govulncheck
Difficulty 2/5 1-3 hours Newbie friendliness 62/100
Maintainers usually reply within 1 day
-
Change wording for init command success messagePossibly taken A pull request linked to this issue is open or already merged. Open
Difficulty 1/5 Under an hour Newbie friendliness 82/100
Maintainers usually reply within 1 day