AUTH-408: bindata: set required-scc

[s-urbaniak]

This sets the required-scc annotation for openshift-apiserver to privileged as openshift-apiserver is a privileged pod.

/cc @deads2k @stlaz

[openshift-ci-robot]

@s-urbaniak: This pull request references AUTH-408 which is a valid jira issue.

In response to this:

This sets the required-scc annotation for openshift-apiserver to privileged as openshift-apiserver is a privileged pod.

/cc @deads2k @stlaz

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.

[openshift-ci]

@s-urbaniak: all tests passed!

Full PR test history. Your PR dashboard.

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. I understand the commands that are listed here.

[s-urbaniak]

Verified that the right SCC is being picked:

$ cat namespaces/openshift-apiserver/core/pods.yaml
...
---
apiVersion: v1
items:
- apiVersion: v1
  kind: Pod
  metadata:
    annotations:
...
      openshift.io/required-scc: privileged
      openshift.io/scc: privileged
...

[s-urbaniak]

just fyi, looking at other PRs it used to be node-exporter before :-|

---
apiVersion: v1
items:
- apiVersion: v1
  kind: Pod
  metadata:
    annotations:
...
      openshift.io/scc: node-exporter

[stlaz]

/lgtm

[mfojtik]

/approve

[openshift-ci]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mfojtik, s-urbaniak, stlaz

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [mfojtik]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment