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

Prune cluster regularly to avoid shortage of resources in PSI #2795

Closed
1 task
mohammedzee1000 opened this issue Apr 1, 2020 · 3 comments
Closed
1 task

Prune cluster regularly to avoid shortage of resources in PSI #2795

mohammedzee1000 opened this issue Apr 1, 2020 · 3 comments
Assignees
@mohammedzee1000
Labels
estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person priority/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
Sprint 183

Comments

@mohammedzee1000
Copy link
Contributor

mohammedzee1000 commented Apr 1, 2020 •
edited

Our clusters on PSI should be pruned regularly in order ensure we do not have shortage of resources

Acceptance

  • Script should regularly prune cluster to ensure continued availability of resources ideally with least impact on usability, as pruning can affect currently deploying stuff

References:
@mohammedzee1000 mohammedzee1000 added priority/Medium Nice to have issue. Getting it done before priority changes would be great. kind/test labels Apr 1, 2020
@mohammedzee1000 mohammedzee1000 added this to For consideration in Sprint 182 via automation Apr 1, 2020
@mohammedzee1000 mohammedzee1000 changed the title Prune cluster regularly to avoid shortage of resources Prune cluster regularly to avoid shortage of resources in PSI Apr 1, 2020
@mohammedzee1000 mohammedzee1000 self-assigned this Apr 1, 2020
@girishramnani girishramnani added triage/ready estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person labels Apr 2, 2020
@girishramnani girishramnani moved this from For consideration to To do in Sprint 182 Apr 2, 2020
@mohammedzee1000 mohammedzee1000 moved this from To do to In progress in Sprint 182 Apr 6, 2020
@mohammedzee1000
Copy link
Contributor Author

mohammedzee1000 commented Apr 6, 2020 •
edited

I have a funtional script(https://gitlab.cee.redhat.com/openshiftdo/PSI/blob/master/lib/openshift/prune_images.sh). I am battle testing it before making it a corn job

@girishramnani girishramnani removed this from In progress in Sprint 182 Apr 20, 2020
@girishramnani girishramnani added this to For consideration in Sprint 183 via automation Apr 20, 2020
@girishramnani girishramnani moved this from For consideration to In progress in Sprint 183 Apr 20, 2020
@mohammedzee1000
Copy link
Contributor Author

We have functional script now in internal repositories
/close

Sprint 183 automation moved this from In progress to Done Apr 20, 2020
@openshift-ci-robot
Copy link
Collaborator

@mohammedzee1000: Closing this issue.

In response to this:

We have functional script now in internal repositories
/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mohammedzee1000 mohammedzee1000

Labels
estimated-size/M (10-20) Rough sizing for Epics. About 1 sprint of work for one person priority/Medium Nice to have issue. Getting it done before priority changes would be great.
Projects
No open projects
Sprint 183
  
Done
Milestone
No milestone
Development

No branches or pull requests
3 participants
@girishramnani @mohammedzee1000 @openshift-ci-robot