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
An alternate setup to setting `--service-account-private-key-file` and `--service-account-key-file` flags is
325
+
to configure an external JWT signer for [external ServiceAccount token signing and key management](#external-serviceaccount-token-signing-and-key-management).
326
+
Note that these setups are mutually exclusive and cannot be configured together.
327
+
322
328
### ServiceAccount admission controller
323
329
324
330
The modification of pods is implemented via a plugin
@@ -544,6 +550,22 @@ Then, delete the Secret you now know the name of:
The kube-apiserver can be configured to use external signer for token signing and token verifying key management.
558
+
This feature enables kubernetes distributions to integrate with key management solutions of their choice (eg: HSMs, cloud KMSes) for service account credential signing and verification.
559
+
To configure kube-apiserver to use external-jwt-signer set the `--service-account-signing-endpoint` flag to the location of a Unix domain socket (UDS) on a filesystem, or be prefixed with an @ symbol and name a UDS in the abstract socket namespace.
560
+
At the configured UDS, shall be an RPC server which implements [ExternalJWTSigner](https://github.com/kubernetes/kubernetes/blob/release-1.32/staging/src/k8s.io/externaljwt/apis/v1alpha1/api.proto).
561
+
The external-jwt-signer must be healthy and be ready to serve supported service account keys for the kube-apiserver to start.
562
+
563
+
Check out [KEP-740](https://github.com/kubernetes/enhancements/tree/master/keps/sig-auth/740-service-account-external-signing) for more details on ExternalJWTSigner.
564
+
565
+
{{< note >}}
566
+
The kube-apiserver flags `--service-account-key-file` and `--service-account-signing-key-file` will continue to be used for reading from files unless `--service-account-signing-endpoint` is set; they are mutually exclusive ways of supporting JWT signing and authentication.
567
+
{{< /note >}}
568
+
547
569
## Clean up
548
570
549
571
If you created a namespace `examplens` to experiment with, you can remove it:
Enable setting `--service-account-signing-endpoint` to make the kube-apiserver use [external signer](/docs/reference/access-authn-authz/service-account-admin#external-serviceaccount-token-signing-and-key-management) for token signing and token verifying key management.
0 commit comments