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 metadata: 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