Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Add docs for bound service account token trigger authentication #1507

Open
wants to merge 1 commit into
base: main
Choose a base branch
from
Open

Add docs for bound service account token trigger authentication #1507

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
14 changes: 14 additions & 0 deletions content/docs/2.17/authentication-providers/bound-service-account-token.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -0,0 +1,14 @@
+++
title = "Bound service account token"
+++

You can pull a service account token into the trigger by defining the `serviceAccountName` of the Kubernetes ServiceAccount and token `expiry` duration.

```yaml
boundServiceAccountToken: # Optional.
- parameter: connectionString # Required - Defined by the scale trigger
serviceAccountName: my-keda-service-account # Required.
expiry: 1h # Required.
```

**Assumptions:** `namespace` is in the same resource as referenced by `scaleTargetRef.name` in the ScaledObject, unless specified otherwise.
15 changes: 14 additions & 1 deletion content/docs/2.17/concepts/authentication.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -240,6 +240,19 @@ secretTargetRef: # Optional.

**Assumptions:** `namespace` is in the same resource as referenced by `scaleTargetRef.name` in the ScaledObject, unless specified otherwise.

### Bound service account token

You can pull a service account token into the trigger by defining the `serviceAccountName` of the Kubernetes ServiceAccount and token `expiry` duration.

```yaml
boundServiceAccountToken: # Optional.
- parameter: connectionString # Required - Defined by the scale trigger
serviceAccountName: my-keda-service-account # Required.
expiry: 1h # Required.
```

**Assumptions:** `namespace` is in the same resource as referenced by `scaleTargetRef.name` in the ScaledObject, unless specified otherwise.

### Hashicorp Vault secret(s)

You can pull one or more Hashicorp Vault secrets into the trigger by defining the authentication metadata such as Vault `address` and the `authentication` method (token | kubernetes). If you choose kubernetes auth method you should provide `role` and `mount` as well.
Expand Down Expand Up @@ -425,4 +438,4 @@ You can tell KEDA to use EKS Pod Identity Webhook via `podIdentity.provider`.
```yaml
podIdentity:
provider: aws-eks # Optional. Default: none
```
```