-
Notifications
You must be signed in to change notification settings - Fork 402
Retrieving Secrets from Vault throws 404 without any error text. #630
Comments
I'm experiencing the same behavior, but this is when trying to sync kv v2 secrets. For context, I'm using external-secrets v6.1.0 and vault 1.6.2 with the following yaml:
And |
|
Sorry @Flydiverny, still adding context, but |
Maybe its failing to get the token, judging by that being the last message before the errors. In that case maybe the vault mount point? But I honestly don't know to much about vault regardless 😄 If it got past the auth it should trigger this log |
No prob! I'm still doing what I can to debug. The auth seems to be working with
So if I'm getting to this point, I'm assuming the auth is working |
Seems reasonable. |
Sounds good... I can try to spin up a dev env at some point today to dig into this a little more |
Here's an untested idea if you want to experiment :) #642 don't have a vault environment setup currently |
This issue is stale because it has been open 90 days with no activity. Remove stale label or comment or this will be closed in 30 days. |
This issue was closed because it has been stalled for 30 days with no activity. |
Retrieving Secrets from Vault throws 404 without any error text.
"payload":{"response":{"statusCode":404,"body":{"errors":[]}}},"msg":"failure while polling the secret <ns>/<external-secret>
I am unable to debug what I am doing wrong.
edit:
more logs
The text was updated successfully, but these errors were encountered: