Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

[release-v1.55] Fix SCC priority so it doesn't get picked for random pods #2469

Commits on Nov 15, 2022

  1. Fix SCC priority so our scc doesn't get picked for random pods

    We create our SCC with `priority: 10` (not sure why), which means
    that it might get picked up by random pods whose service account is privileged enough to access all SCCs:
    ```bash
    $ oc get pods -n openshift-cluster-storage-operator cluster-storage-operator-5648cb555d-zh76b  -o yaml| grep scc
        openshift.io/scc: containerized-data-importer
    ```
    Happens because it can physically do that
    ```bash
    $ oc get clusterrolebinding cluster-storage-operator-role -o yaml | grep cluster-admin
      name: cluster-admin
    ```
    A nice readout about this in context of the openshift oauth pods:
    https://access.redhat.com/solutions/4727461
    
    Signed-off-by: Alex Kalenyuk <akalenyu@redhat.com>
    akalenyu authored and kubevirt-bot committed Nov 15, 2022
    Configuration menu
    Copy the full SHA
    dcc9ebd View commit details
    Browse the repository at this point in the history