You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
prevents Kubernetes from automatically creating these tokens for
186
186
ServiceAccounts. `LegacyServiceAccountTokenNoAutoGeneration` is enabled
187
187
by default; in other words, Kubernetes does not create these tokens.
188
188
189
+
{{< note >}}
190
+
For applications running outside your Kubernetes cluster, you might be considering
191
+
creating a long-lived ServiceAccount token that is stored in a Secret. This allows authentication, but the Kubernetes project recommends you avoid this approach.
192
+
Long-lived bearer tokens represent a security risk as, once disclosed, the token
193
+
can be misused. Instead, consider using an alternative. For example, your external
194
+
application can authenticate using a well-protected private key `and` a certificate,
195
+
or using a custom mechanism such as an [authentication webhook](/docs/reference/access-authn-authz/authentication/#webhook-token-authentication) that you implement yourself.
196
+
197
+
You can also use TokenRequest to obtain short-lived tokens for your external application.
198
+
{{< /note >}}
199
+
189
200
## Authenticating service account credentials {#authenticating-credentials}
0 commit comments