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
identityId: <identity-id> # Optional. Only used by azure & azure-workload providers.
337
337
roleArn: <role-arn> # Optional. Only used by aws provider.
338
338
identityOwner: keda|workload # Optional. Only used by aws provider.
339
339
```
340
340
341
-
#### Azure Pod Identity
342
-
343
-
> [DEPRECATED: This will be removed in KEDA v2.15](https://github.com/kedacore/keda/discussions/5362)
344
-
345
-
Azure Pod Identity is an implementation of [**Azure AD Pod Identity**](https://github.com/Azure/aad-pod-identity) which lets you bind an [**Azure Managed Identity**](https://docs.microsoft.com/en-us/azure/active-directory/managed-identities-azure-resources/) to a Pod in a Kubernetes cluster as delegated access - *Don't manage secrets, let Azure AD do the hard work*.
346
-
347
-
You can tell KEDA to use Azure AD Pod Identity via `podIdentity.provider`.
348
-
349
-
```yaml
350
-
podIdentity:
351
-
provider: azure # Optional. Default: none
352
-
identityId: <identity-id> # Optional. Default: Identity linked with the label set when installing KEDA.
353
-
```
354
-
355
-
Azure AD Pod Identity will give access to containers with a defined label for `aadpodidbinding`. You can set this label on the KEDA operator deployment. This can be done for you during deployment with Helm with `--set podIdentity.activeDirectory.identity={your-label-name}`.
356
-
357
-
You can override the identity that was assigned to KEDA during installation, by specifying an `identityId` parameter under the `podIdentity` field. This allows end-users to use different identities to access various resources which is more secure than using a single identity that has access to multiple resources.
358
-
359
341
#### Azure Workload Identity
360
342
361
343
[**Azure AD Workload Identity**](https://github.com/Azure/azure-workload-identity) is the newer version of [**Azure AD Pod Identity**](https://github.com/Azure/aad-pod-identity). It lets your Kubernetes workloads access Azure resources using an
@@ -443,17 +425,4 @@ You can tell KEDA to use EKS Pod Identity Webhook via `podIdentity.provider`.
443
425
```yaml
444
426
podIdentity:
445
427
provider: aws-eks # Optional. Default: none
446
-
```
447
-
448
-
#### AWS Kiam Pod Identity
449
-
450
-
> [DEPRECATED: This will be removed in KEDA v2.15](https://github.com/kedacore/keda/discussions/5342)
451
-
452
-
[**Kiam**](https://github.com/uswitch/kiam/) lets you bind an AWS IAM Role to a pod using an annotation on the pod.
453
-
454
-
You can tell KEDA to use Kiam via `podIdentity.provider`.
Copy file name to clipboardexpand all lines: content/docs/2.15/scalers/aws-cloudwatch.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -58,7 +58,7 @@ triggers:
58
58
- `dimensionValue` - Supports specifying multiple dimension values by using ";" as a separator i.e. dimensionValue: queue1;queue2 (Optional, Required when `expression` is not specified)
59
59
- `expression`- Supports query with [expression](https://docs.aws.amazon.com/AmazonCloudWatch/latest/monitoring/cloudwatch-metrics-insights-querylanguage.html) (Optional, Required when `dimensionName` & `dimensionValue` are not specified)
60
60
61
-
- `identityOwner` - Receive permissions for CloudWatch via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` and `aws-kiam` authentications)
61
+
- `identityOwner` - Receive permissions for CloudWatch via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` authentication)
62
62
63
63
> When `identityOwner` set to `operator` - the only requirement is that the KEDA operator has the correct IAM permissions on the CloudWatch. Additional Authentication Parameters are not required.
64
64
@@ -81,7 +81,7 @@ You can use `TriggerAuthentication` CRD to configure authentication by providing
81
81
82
82
**Role based authentication:**
83
83
84
-
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated only applies for `aws-eks` and `aws-kiam` authentications, for `aws` is set in the auth)
84
+
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated and only applies for `aws-eks` authentication, for `aws` is set in the auth)
Copy file name to clipboardexpand all lines: content/docs/2.15/scalers/aws-dynamodb-streams.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ triggers:
33
33
- `tableName`- The target DynamoDB table to which the stream belongs.
34
34
- `shardCount` - The target value that a DynamoDB streams consumer can handle. (Default: `2`, Optional)
35
35
- `activationShardCount`- Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds). (Default: `0`, Optional)
36
-
- `identityOwner` - Receive permissions on the DynamoDB and DynamoDB Streams via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` and `aws-kiam` authentications)
36
+
- `identityOwner` - Receive permissions on the DynamoDB and DynamoDB Streams via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` authentication)
37
37
38
38
> When `identityOwner` set to `operator` - the only requirement is that the KEDA operator has the correct IAM permissions on the DynamoDB and Dynamodb Streams. Additional Authentication Parameters are not required.
39
39
@@ -43,11 +43,11 @@ You can use `TriggerAuthentication` CRD to configure the authenticate by providi
43
43
44
44
**Pod identity based authentication:**
45
45
46
-
- `podIdentity.provider`- Needs to be set to either `aws-kiam` or `aws-eks` on the `TriggerAuthentication` and the pod/service account must be configured correctly for your pod identity provider.
46
+
- `podIdentity.provider`- Needs to be set on the `TriggerAuthentication` and the pod/service account must be configured correctly for your pod identity provider.
47
47
48
48
**Role based authentication:**
49
49
50
-
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated only applies for `aws-eks` and `aws-kiam` authentications, for `aws` is set in the auth)
50
+
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated and only applies for `aws-eks` authentication, for `aws` is set in the auth)
Copy file name to clipboardexpand all lines: content/docs/2.15/scalers/aws-dynamodb.md
+3-3
Original file line number
Diff line number
Diff line change
@@ -45,7 +45,7 @@ triggers:
45
45
- `expressionAttributeNames`- one or more substitution tokens for attribute names in an expression. Defined as JSON.
46
46
- `keyConditionExpression`- the condition that specifies the key values for items to be retrieved by the Query action.
47
47
- `expressionAttributeValues`- one or more values that can be substituted in an expression. Defined as JSON.
48
-
- `identityOwner` - Receive permissions on the DynamoDB Table via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` and `aws-kiam` authentications)
48
+
- `identityOwner` - Receive permissions on the DynamoDB Table via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` authentication)
49
49
50
50
> When `identityOwner` set to `operator` - the only requirement is that the KEDA operator has the correct IAM permissions on the DynamoDB Table. Additional Authentication Parameters are not required.
51
51
@@ -55,11 +55,11 @@ You can use `TriggerAuthentication` CRD to configure the authenticate by providi
55
55
56
56
**Pod identity based authentication:**
57
57
58
-
- `podIdentity.provider`- Needs to be set to either `aws-kiam` or `aws-eks` on the `TriggerAuthentication` and the pod/service account must be configured correctly for your pod identity provider.
58
+
- `podIdentity.provider`- Needs to be set on the `TriggerAuthentication` and the pod/service account must be configured correctly for your pod identity provider.
59
59
60
60
**Role based authentication:**
61
61
62
-
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated only applies for `aws-eks` and `aws-kiam` authentications, for `aws` is set in the auth)
62
+
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated and only applies for `aws-eks` authentication, for `aws` is set in the auth)
Copy file name to clipboardexpand all lines: content/docs/2.15/scalers/aws-kinesis.md
+2-2
Original file line number
Diff line number
Diff line change
@@ -33,7 +33,7 @@ triggers:
33
33
- `activationShardCount`- Target value for activating the scaler. Learn more about activation [here](./../concepts/scaling-deployments.md#activating-and-scaling-thresholds). (Default: `0`, Optional)
34
34
- `awsRegion`- AWS Region for the Kinesis Stream.
35
35
- `awsEndpoint` - Endpoint URL to override the default AWS endpoint. (Default: `""`, Optional)
36
-
- `identityOwner` - Receive permissions on the Kinesis Stream via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` and `aws-kiam` authentications)
36
+
- `identityOwner` - Receive permissions on the Kinesis Stream via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` authentication)
37
37
38
38
> When `identityOwner` set to `operator` - the only requirement is that the KEDA operator has the correct IAM permissions on the Kinesis Stream. Additional Authentication Parameters are not required.
39
39
@@ -45,7 +45,7 @@ You can use `TriggerAuthentication` CRD to configure the authenticate by providi
45
45
46
46
**Role based authentication:**
47
47
48
-
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated only applies for `aws-eks` and `aws-kiam` authentications, for `aws` is set in the auth)
48
+
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated and only applies for `aws-eks` authentication, for `aws` is set in the auth)
Copy file name to clipboardexpand all lines: content/docs/2.15/scalers/aws-sqs.md
+4-4
Original file line number
Diff line number
Diff line change
@@ -40,7 +40,7 @@ triggers:
40
40
- `scaleOfDelayed` - Indication of whether or not to include delayed messages when calculating the number of SQS messages. (default: false, Optional)
41
41
- `awsRegion`- AWS Region for the SQS Queue.
42
42
- `awsEndpoint` - Endpoint URL to override the default AWS endpoint. (Default: `""`, Optional)
43
-
- `identityOwner` - Receive permissions on the SQS Queue via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` and `aws-kiam` authentications)
43
+
- `identityOwner` - Receive permissions on the SQS Queue via Pod Identity or from the KEDA operator itself (see below). (DEPRECATED: This parameter is deprecated as of KEDA v2.13 and will be removed in version `3`, Values: `pod`, `operator`, Default: `pod`, Optional, This field only applies for `aws-eks` authentication)
44
44
45
45
> When `identityOwner` set to `operator` - the only requirement is that the KEDA operator has the correct IAM permissions on the SQS queue. Additional Authentication Parameters are not required.
46
46
@@ -50,11 +50,11 @@ You can use `TriggerAuthentication` CRD to configure the authenticate by providi
50
50
51
51
**Pod identity based authentication:**
52
52
53
-
- `podIdentity.provider`- Needs to be set to either `aws-kiam` or `aws-eks` on the `TriggerAuthentication` and the pod/service account must be configured correctly for your pod identity provider.
53
+
- `podIdentity.provider`- Needs to be set on the `TriggerAuthentication` and the pod/service account must be configured correctly for your pod identity provider.
54
54
55
55
**Role based authentication:**
56
56
57
-
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated only applies for `aws-eks` and `aws-kiam` authentications, for `aws` is set in the auth)
57
+
- `awsRoleArn`- Amazon Resource Names (ARNs) uniquely identify AWS resource. (This field is deprecated and only applies for `aws-eks` authentication, for `aws` is set in the auth)
0 commit comments