Which OpenShift object represents a non-human identity used by pods to access resources?

Which OpenShift object represents a non-human identity used by pods to access resources?

• A. ServiceAccount
• B. SecurityContext
• C. PodSecurityPolicy
• D. Namespace

Answer: (A)

Pods access resources in the cluster using a non-human identity called a ServiceAccount. A ServiceAccount is an object that represents an application’s identity for pods, enabling them to authenticate to the API server and perform actions based on RBAC permissions. When a pod runs, it receives credentials for its ServiceAccount (a token) that is mounted into the pod, and the pod’s processes use this token to access other resources. You can grant specific permissions by binding the ServiceAccount to roles with RoleBinding or ClusterRoleBinding, and every project/namespace has a default ServiceAccount if none is specified. SecurityContext controls container-level privileges, not identity. PodSecurityPolicy (now deprecated in favor of alternatives) governs security constraints on pods. Namespace defines a scope for resources, not an identity.

Pods access resources in the cluster using a non-human identity called a ServiceAccount. A ServiceAccount is an object that represents an application’s identity for pods, enabling them to authenticate to the API server and perform actions based on RBAC permissions. When a pod runs, it receives credentials for its ServiceAccount (a token) that is mounted into the pod, and the pod’s processes use this token to access other resources. You can grant specific permissions by binding the ServiceAccount to roles with RoleBinding or ClusterRoleBinding, and every project/namespace has a default ServiceAccount if none is specified.

SecurityContext controls container-level privileges, not identity. PodSecurityPolicy (now deprecated in favor of alternatives) governs security constraints on pods. Namespace defines a scope for resources, not an identity.