When a Pod is created in a given namespace and no specific service account is explicitly defined in its manifest, Kubernetes automatically assigns the default service account for that particular namespace to the Pod.
Every Kubernetes namespace is initialized with a default service account. This default service account is used as a fallback for any Pods that do not specify a serviceAccountName in their spec.
The default service account, by default, has no special permissions beyond what Kubernetes grants to all authenticated principals for API discovery, assuming Role-Based Access Control (RBAC) is enabled in the cluster. If a Pod requires specific permissions to interact with the Kubernetes API or other resources, a dedicated service account with the necessary roles and role bindings should be created and explicitly assigned to the Pod.
This section is not available anymore. Please use the main Exam Page.KCNA Exam Questions
Log in to ExamTopics
Sign in:
Community vote distribution
A (35%)
C (25%)
B (20%)
Other
Most Voted
A voting comment increases the vote count for the chosen answer by one.
Upvoting a comment with a selected answer will also increase the vote count towards that answer by one.
So if you see a comment that you already agree with, you can upvote it instead of posting a new comment.
8378ffe
2 months, 2 weeks agoZangi
4 months, 1 week ago