Linux repositories inspector




OpenShift Open Source Container Management by Red Hat


oadm policy scc-review - Checks which ServiceAccount can create a Pod


oadm policy scc-review [OPTIONS]


Checks which Service Account can create a Pod. The Pod is inferred from the PodTemplateSpec in the provided resource. If no Service Account is provided the one specified in podTemplateSpec.spec.serviceAccountName is used, unless it is empty, in which case "default" is used. If Service Accounts are provided the podTemplateSpec.spec.serviceAccountName is ignored.


If true, ignore any errors in templates when a field or map key is missing in the template. Only applies to golang and jsonpath output formats.
-f, --filename=[]
Filename, directory, or URL to files Filename, directory, or URL to a file identifying the resource to get from a server.
When using the default or custom-column output format, don’t print headers (default print headers).
-o, --output=""
Output format. One of: json|yaml|wide|name|custom-columns=...|custom-columns-file=...|go-template=...|go-template-file=...|jsonpath=...|jsonpath-file=... See custom columns [ [la][ra]], golang template [ [la][ra]] and jsonpath template [ [la][ra]].
-R, --recursive=false
Process the directory used in -f, --filename recursively. Useful when you want to manage related manifests organized within the same directory.
-z, --serviceaccount=[]
service account in the current namespace to use as a user
-a, --show-all=false
When printing, show all resources (default hide terminated pods.)
When printing, show all labels as the last column (default hide labels column)
If non-empty, sort list types using this field specification. The field specification is expressed as a JSONPath expression (e.g. ’{}’). The field in the API resource specified by this JSONPath expression must be an integer or a string.
Template string or path to template file to use when -o=go-template, -o=go-template-file. The template format is golang templates [ [la][ra]].


Username to impersonate for the operation
Group to impersonate for the operation, this flag can be repeated to specify multiple groups.
Path to the file container Azure container registry configuration information.
Path to a cert file for the certificate authority
Path to a client certificate file for TLS
Path to a client key file for TLS
The name of the kubeconfig cluster to use
Path to the config file to use for CLI requests.
The name of the kubeconfig context to use
The Google Cloud Platform Service Account JSON Key to use for authentication.
If true, the server’s certificate will not be checked for validity. This will make your HTTPS connections insecure
Maximum number of seconds between log flushes
Require server version to match client version
-n, --namespace=""
If present, the namespace scope for this CLI request
The length of time to wait before giving up on a single server request. Non-zero values should contain a corresponding time unit (e.g. 1s, 2m, 3h). A value of zero means don’t timeout requests.
The address and port of the Kubernetes API server
Bearer token for authentication to the API server
The name of the kubeconfig user to use
Print version information and quit


  # Check whether Service Accounts sa1 and sa2 can admit a Pod with TemplatePodSpec specified in my_resource.yaml
  # Service Account specified in myresource.yaml file is ignored
  $ oadm policy scc-review -z sa1,sa2 -f my_resource.yaml

  # Check whether Service Accounts system:serviceaccount:bob:default can admit a Pod with TemplatePodSpec specified in my_resource.yaml
  $  oadm policy scc-review -z system:serviceaccount:bob:default -f my_resource.yaml

  # Check whether Service Account specified in my_resource_with_sa.yaml can admit the Pod
  $ oadm policy scc-review -f my_resource_with_sa.yaml

  # Check whether default Service Account can admit the Pod, default is taken since no Service Account is defined in myresource_with_no_sa.yaml
  $  oadm policy scc-review -f myresource_with_no_sa.yaml


June 2016, Ported from the Kubernetes man-doc generator
⇧ Top