| Field | Type | Description | Value(s) |
|---|---|---|---|
kubeconfig | string | Kubeconfig kube-apiserver uses to connect to the authentication webhook. The kubeconfig should be self-contained: kube-apiserver can’t access any files on the host, so certificates and keys should be specified inline ( certificate-authority-data, client-certificate-data,client-key-data), and tokenFile, exec and auth-provider are not supported.If the certificate authority is not specified, kube-apiserver uses the trusted root CAs of the machine. | |
version | string | The API version of the authentication.k8s.io TokenReview to send to and expect from the webhook.Defaults to the kube-apiserver default ( v1beta1). | v1v1beta1 |
cacheTTL | Duration | The duration to cache responses from the webhook token authenticator. Defaults to the kube-apiserver default (2 minutes), set to 0s to disable caching. |
Kubernetes
KubeAuthenticationWebhookConfig
KubeAuthenticationWebhookConfig configures kube-apiserver webhook token authentication.
Bearer tokens which are not recognized by other authenticators are sent to the webhook
(a TokenReview request) to be authenticated, e.g. for
aws-iam-authenticator.
Talos writes the kubeconfig to a file inside the kube-apiserver static pod and sets the
--authentication-token-webhook-* flags of kube-apiserver accordingly,
so these flags are not allowed in KubeAPIServerConfig extraArgs.