Bug 1805830

Summary: clusteroperator/kube-apiserver related objects needs to include SCC
Product: OpenShift Container Platform Reporter: David Eads <deads>
Component: kube-apiserverAssignee: Venkata Siva Teja Areti <vareti>
Status: CLOSED ERRATA QA Contact: Ke Wang <kewang>
Severity: high Docs Contact:
Priority: high    
Version: 4.4CC: aos-bugs, mfojtik, xxia
Target Milestone: ---   
Target Release: 4.5.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-07-13 17:16:59 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 David Eads 2020-02-21 15:52:08 UTC
There shouldn't be that many SCCs, but we need to see what's present and when to debug pod creation latency.

Comment 3 Ke Wang 2020-03-18 02:33:49 UTC
Verified with OCP build 4.5.0-0.nightly-2020-03-17-213400, the related resource  securitycontextconstraints is already in.

$ oc get co/kube-apiserver -o json | jq .status.relatedObjects[2]
{
  "group": "security.openshift.io",
  "name": "",
  "resource": "securitycontextconstraints"
}


$ oc describe co/kube-apiserver | grep -A2 'security.openshift.io'
    Group:     security.openshift.io
    Name:      
    Resource:  securitycontextconstraints

Comment 5 errata-xmlrpc 2020-07-13 17:16:59 UTC
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409