Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Don't try to create limit range for deleted namespace #1

Closed
sgdan opened this issue Jun 23, 2020 · 0 comments
Closed

Don't try to create limit range for deleted namespace #1

sgdan opened this issue Jun 23, 2020 · 0 comments
Assignees
@sgdan

Comments

@sgdan
Copy link
Owner

sgdan commented Jun 23, 2020

Steps to reproduce:

  • Delete a namespace in the cluster

Expected result:

  • Reaper stops trying to set limit range for deleted namespace

Actual result:

  • Reaper logs that it's trying to create default limit range for deleted namespace
@sgdan sgdan self-assigned this Jun 27, 2020
sgdan added a commit that referenced this issue Jun 27, 2020
@sgdan
Ensure namespaces get deleted
10fc8a1 
- can't reproduce #1 but added code to ensure namespaces get removed if they have been deleted from the cluster
- update backend-dev to run go code directly rather than building docker image
- make timings configurable and add to README
- add error handling to ranger code to avoid #1 scenario
- disable CORS by default, only needed for dev
@sgdan sgdan closed this as completed Jun 30, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@sgdan sgdan

Labels
None yet
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
1 participant
@sgdan