v1 ยท Namespaced Resource


ServiceAccount binds together: * a name, understood by users, and perhaps by peripheral systems, for an identity * a principal that can be authenticated and authorized * a set of secrets

Looking for some examples?

There are 1 examples of ServiceAccount that you can use as a starting point to create your own.

apiVersion: v1
kind: ServiceAccount
  name: my-app-service-account # just give it a name and then use it on your Pods/Deployments/etc
automountServiceAccountToken: false # you can opt out of the API credential automounting
Tired of using Kubectl? ๐Ÿ˜“

Give Aptakube a go โ€” a modern, lightweight Kubernetes interface.

Screenshot of Aptakube showing a list of pods from 2 clusters in a single view