Lineage
read-only · v1.0
static mock demo — no cluster connection, no oc, no credentials
Static mock demo. This page uses a small bundled sample dataset. It does not connect to a cluster, run oc, or read local credentials.

ServiceAccount default in ci

Pods (0)

No pods running as this ServiceAccount.

Jobs running as this ServiceAccount (0)

None.

CronJobs running as this ServiceAccount (0)

None.

Bindings referencing this ServiceAccount

Every binding whose subject list names this SA — split by scope.

RoleBindings in ci (0)

None.

RoleBindings in other namespaces (0)

None.

ClusterRoleBindings (0)

None.

Direct SCC eligibility (1)

SCCs this ServiceAccount can use because its principal is listed directly in scc.users, or because scc.groups includes a group the principal belongs to (system:authenticated, system:serviceaccounts, or system:serviceaccounts:ci). This is not the full effective SCC set — RBAC use grants on securitycontextconstraints objects also admit pods, and those are listed on each SCC's detail page under Potential subjects.

SCCPriorityGranted viaPrivileged
restricted-v2 group system:authenticated no

Reach

Where this subject's permissions land. Cluster-wide grants reach every namespace; namespace-scoped grants are listed individually.

This subject has no bindings (direct or via group membership).

Effective permissions (0 paths)

No paths.