Keda & Hashicorp Vault integration - ExpiredToken #6792
Replies: 1 comment
|
Sorry guys my bad, keda leaves the error but actually try to ask vault a new token. So it's working normally |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Hi all,
Context:
What I'm trying to do is to configure Keda with hashicorp vault using the kubernetes authentication and the service account of keda operator.
I'm trying to authenticate to aws using his secret engine and get temporary sts credentials. Everything works fine but I noticed that after the expiration of the token expires, Keda does not fetch a new one and we have an error like this:
(keda-operator)` 2025-05-21T10:49:27Z ERROR aws_sqs_queue_scaler Error getting queue length {"type": "ScaledObject", "namespace": "default", "name": "my-scaledobject-sqs-test", "error": "operation error SQS: GetQueueAttributes, https response error StatusCode: 403, RequestID: d439b2b4-52c2-518f-99e1-d213e3356a40, api error ExpiredToken: The security token included in the request is expired"}The temporary solution is to restart everytime the keda operator pod or to delete and re-create the triggerAuthentication, do you have any idea if it's something that I'm doing wrong or if it's a Keda normal behaviour? Thanks a lot
All reactions