Light, fluffy, and always free - The AWS Local Emulator alternative
docs(lambda): qualify which kubeconfig auth methods the Kubernetes executor supports (#2978)
Priamo Germosen2b531dad3ad1
diff --git a/docs/services/lambda.md b/docs/services/lambda.mdindex 5b0be8cb1c..fda52bd442 100644--- a/docs/services/lambda.md+++ b/docs/services/lambda.md@@ -313,7 +313,10 @@ environment as a Kubernetes pod instead of a Docker container. This is designedfor CI/CD clusters where privileged containers and `docker.sock` access are notallowed. Floci talks to the cluster through the standard Kubernetes API: whenrunning inside the cluster it uses its ServiceAccount, and when running outside-it uses your local kubeconfig.+it uses your local kubeconfig. Only an inline static bearer `token` or a+client-certificate/client-key credential with a PKCS#8 private key is+supported; `tokenFile`, exec, and auth-provider credential plugins+(`aws eks get-token`, gcloud, etc.) are not, and fail with a named error.How an invocation works: