Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1623222

Summary: [free-int] apiservice pods should be scheduled on infra nodes
Product: OpenShift Container Platform Reporter: Justin Pierce <jupierce>
Component: InstallerAssignee: Scott Dodson <sdodson>
Status: CLOSED WONTFIX QA Contact: Johnny Liu <jialiu>
Severity: low Docs Contact:
Priority: unspecified    
Version: 3.11.0CC: aos-bugs, jokerman, mmccomas, sdodson
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-01-31 15:54:25 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:
Attachments:
Description Flags
critical pod scheduled on standard compute none

Description Justin Pierce 2018-08-28 19:14:45 UTC 
Created attachment 1479342 [details]
critical pod scheduled on standard compute

Description of problem:
When an apiservice pod is scheduled on a standard compute node, it is possible to impact the operation of the API: https://bugzilla.redhat.com/show_bug.cgi?id=1623108

Version-Release number of the following components:
3.11

How reproducible:
100%

Steps to Reproduce:
1. Allow apiservice pod to be scheduled on Ready but somehow compromised node such as: https://bugzilla.redhat.com/show_bug.cgi?id=1623108
2.
3.

Actual results:
In the case of https://bugzilla.redhat.com/show_bug.cgi?id=1623108, this condition indefinitely blocks calls to 'oc delete project <p>'. 

Expected results:
Resources critical to cluster operation should be restricted to infra nodes.
Comment 1 Scott Dodson 2018-08-28 19:29:27 UTC 
This comes from roles/metrics_server/ I think though we should have a wider discussion as to whether or not all aggregated APIs should be scheduled to master, infra, or compute nodes.
Comment 3 Scott Dodson 2019-01-31 15:54:25 UTC 
There appear to be no active cases related to this bug. As such we're closing this bug in order to focus on bugs that are still tied to active customer cases. Please re-open this bug if you feel it was closed in error or a new active case is attached.