-
Notifications
You must be signed in to change notification settings - Fork 10
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.
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
Support AAD Pod Identity #49
Comments
Hey, |
I've been trying to understand if I can deploy the scaler with # Create KEDA scaled object to scale order processor application.
apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
name: azure-cosmosdb-auth
spec:
podIdentity:
provider: azure-workload
---
apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
name: cosmosdb-order-processor-scaledobject
namespace: cosmosdb-order-processor
spec:
pollingInterval: 20
scaleTargetRef:
name: cosmosdb-order-processor
triggers:
- type: external
authenticationRef:
name: azure-cosmosdb-auth # authenticationRef would need either podIdentity or define a connection parameter
metadata:
scalerAddress: external-scaler-azure-cosmos-db.cosmosdb-order-processor:4050
endpoint: https://{Cosmos DB Account Name}.documents.azure.com:443/ # update as per your environment
databaseId: StoreDatabase
containerId: OrderContainer
LeaseEndpoint: https://{Cosmos DB Account Name}.documents.azure.com:443/ # update as per your environment
leaseDatabaseId: StoreDatabase
leaseContainerId: OrderProcessorLeases
processorName: OrderProcessor It looks like Azure Workload Identity is supported in KEDA. The only thing missing is the actual support in code that I tried adding in #68. State of the code is little confusing though:
|
Add support for using pod identity binding to access the cosmos db via account endpoint only.
Use-Case
Our cosmos dbs are set up to only use AD for access. We would like to create a role with the access that this scaler will need and use that and the account endpoint for access. We would then not need to have connection strings in configuration.
The text was updated successfully, but these errors were encountered: