Bug 1403929

Summary:	[RFE] Deploy certain pods on special nodes
Product:	OpenShift Container Platform	Reporter:	Alexander Koksharov <akokshar>
Component:	RFE	Assignee:	Derek Carr <decarr>
Status:	CLOSED DEFERRED	QA Contact:	Xiaoli Tian <xtian>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	3.3.0	CC:	akokshar, aos-bugs, decarr, gmarcote, jokerman, mbarrett, michael.voegele, mmccomas, simon.gunzenreiner
Target Milestone:	---	Flags:	erich: needinfo? (akokshar)
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:	2018-03-12 13:54:36 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:

Description Alexander Koksharov 2016-12-12 16:14:26 UTC

Description of problem:

As an administrator, I want a possibility to deploy certain application on a predefined node regardless of nodeSelector set for a project. Need the following to be possible:
- normally deploy all pods in a project to some default application nodes (done via defaultNodeSelector or nodeSelector on project level)
- in some special cases, deploy the special pods IN THE SAME PROJECT to some special nodes
- it should not be possible that the normal pods land on a special node


Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 1 Derek Carr 2016-12-12 16:27:19 UTC

I would recommend the use of taints/tolerations for this feature.

The special node would have the taint applied that had NoScheduleNoAdmitNoExecute operator, and only the special pod would have the toleration for that taint.  This would prevent normal pods from landing on the special node.

Comment 7 Eric Rich 2018-03-12 13:54:36 UTC

This bug has been identified as a dated (created more than 3 months ago) bug. 
This bug has been triaged (has a trello card linked to it), or reviewed by Engineering/PM and has been put into the product backlog, 
however this bug has not been slated for a currently planned release (3.9, 3.10 or 3.11), which cover our releases for the rest of the calendar year. 

As a result of this bugs age, state on the current roadmap and PM Score (being below 70), this bug is being Closed - Differed, 
as it is currently not part of the products immediate priorities.

Please see: https://docs.google.com/document/d/1zdqF4rB3ea8GmVIZ7qWCVYUaQ7-EexUrQEF0MTwdDkw/edit for more details.