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.

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

lifecycle management scenarios #43

Open
rhs opened this issue Oct 30, 2018 · 2 comments
Open

lifecycle management scenarios #43

rhs opened this issue Oct 30, 2018 · 2 comments

Comments

@rhs
Copy link
Contributor

rhs commented Oct 30, 2018

  • ability to specify up front that a claim should automatically expire after a specified time would be handy for CI
  • ability to "group" claims somehow and delete the whole group
@rhs rhs changed the title ability to specify up front that a claim should automatically expire after a specified time would be handy for CI lifecycle management scenarios Oct 30, 2018
@plombardi89
Copy link
Contributor

  1. Yea the expiration system needs to be implemented. I have wanted exactly what you described. Right now claims never expire at all and really there needs to be user-configurable ones as well system-imposed ones.

  2. The UX for this could be better, but some combination of kubernaut claims list, grep and kubernaut claims delete <claim names...> can handle this if you use a common naming strategy.

@rhs
Copy link
Contributor Author

rhs commented Nov 1, 2018

Good point on (2), I hadn't thought about that.

FYI, the main context for this is that I want to have an idiot proof way to avoid "leaking" resources from CI. My strategy for doing that right now works, but I wouldn't call it idiot proof.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants