Bug 1468547

Summary:	RFE: support pruning Jobs and Pods
Product:	OpenShift Container Platform	Reporter:	Jaspreet Kaur <jkaur>
Component:	RFE	Assignee:	Eric Paris <eparis>
Status:	CLOSED WONTFIX	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	3.5.0	CC:	aos-bugs, eparis, erich, jmalde, jokerman, marc.jadoul, mchappel, mmccomas, mruzicka, obockows, rekhan
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2019-06-12 11:56:01 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Jaspreet Kaur 2017-07-07 11:37:09 UTC

3. What is the nature and description of the request?

We would like to request that "oc adm prune" be extended to include Jobs and Pods, so that we can prune out the 1000s of Completed pods 

 

4. Why does the customer need this? (List the business requirements here)

To avoid a build up of unused resources.
 

5. How would the customer like to achieve this? (List the functional requirements here)

Enhancement to oc adm prune

Comment 2 Mark Chappell 2017-07-07 11:55:27 UTC

Similar to what I think may have been the original intent of https://bugzilla.redhat.com/show_bug.cgi?id=1435228

However, the card spawned as a result of that bz seems to be focused on running oc adm prune from inside a job, rather than pruning the completed jobs:
https://trello.com/c/5T5MsGCj/784-jobs-as-an-administrator-of-openshift-i-want-prune-commands-to-run-as-jobs-on-the-cluster

(We already run oc adm prune from within containers using "oc observe", to prune specific namespaces when they start build configs)

Comment 5 Marc Jadoul 2017-09-28 09:04:25 UTC

Hello,

I opened the following Redhat support case which seems related on Openshift 3.4.
CASE 01941544

Currently:
*    successfulJobsHistoryLimit: 5"
    failedJobsHistoryLimit: 5"
Seems to have no effect in 3.4?

* Job nubers are not random and are reccuring. Old existing complete jobs block new job scheduling!

* There is no way to delete jobs except ... oc delete jobs of course?

Regards,
Marc

Comment 15 Kirsten Newcomer 2019-06-12 11:56:01 UTC

With the introduction of OpenShift 4, Red Hat has delivered or roadmapped a substantial number of features based on feedback by our customers.  Many of the enhancements encompass specific RFEs which have been requested, or deliver a comparable solution to a customer problem, rendering an RFE redundant.

This bz (RFE) has been identified as a feature request not yet planned or scheduled for an OpenShift release and is being closed. 

If this feature is still an active request that needs to be tracked, Red Hat Support can assist in filing a request in the new JIRA RFE system, as well as provide you with updates as the RFE progress within our planning processes. Please open a new support case: https://access.redhat.com/support/cases/#/case/new 

Opening a New Support Case: https://access.redhat.com/support/cases/#/case/new 

As the new Jira RFE system is not yet public, Red Hat Support can help answer your questions about your RFEs via the same support case system.