Skip to content

Commit 4747731

Browse files
Fix --service-account-key-file description
--service-account-key-file flag to the kube-api-server is used to verify ServiceAccount tokens (and not to sign them). --service-account-signing-key-file is the kube-api-server flag that's used to sign ServiceAccount tokens (short-lived ones). --service-account-private-key-file is the kube-controller-manager flag that's used to sign ServiceAccount tokens (long-lived ones).
1 parent 9193053 commit 4747731

File tree

1 file changed

+4
-2
lines changed

1 file changed

+4
-2
lines changed

content/en/docs/reference/access-authn-authz/authentication.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -171,8 +171,10 @@ how to manage these tokens with `kubeadm`.
171171
A service account is an automatically enabled authenticator that uses signed
172172
bearer tokens to verify requests. The plugin takes two optional flags:
173173

174-
* `--service-account-key-file` A file containing a PEM encoded key for signing bearer tokens.
175-
If unspecified, the API server's TLS private key will be used.
174+
* `--service-account-key-file` File containing PEM-encoded x509 RSA or ECDSA
175+
private or public keys, used to verify ServiceAccount tokens. The specified file
176+
can contain multiple keys, and the flag can be specified multiple times with
177+
different files. If unspecified, --tls-private-key-file is used.
176178
* `--service-account-lookup` If enabled, tokens which are deleted from the API will be revoked.
177179

178180
Service accounts are usually created automatically by the API server and

0 commit comments

Comments
 (0)