KEDA Hashicorp vault service account token request

[BojanZelic]

Allows users to authenticate to vault via a service account in the scaledObject's namespace;

ex:

apiVersion: keda.sh/v1alpha1
kind: TriggerAuthentication
metadata:
  name: my-trigger-auth
  namespace: mynamespace
spec:
...
  hashiCorpVault:
    address: {hashicorp-vault-address}
    credential:
      serviceAccountName: default

apiVersion: keda.sh/v1alpha1
kind: ScaledObject
metadata:
  name: my-scaled-object
  namespace: mynamespace
spec:
  triggers:
  - authenticationRef:
      name: my-trigger-auth
      kind: TriggerAuthentication
    metadata:
...

would use the JWT token from the default service account in the mynamespace namespace

This allows users to set more fine-grained permissions in vault.

Checklist

• I have verified that my change is according to the deprecations & breaking changes policy
• Tests have been added
• Changelog has been updated and is aligned with our changelog requirements
• A PR is opened to update our Helm chart Allow Keda to request SA tokens charts#728
• A PR is opened to update the documentation on document Vault authentication via cross-namespace service accounts keda-docs#1521
• Commits are signed with Developer Certificate of Origin (DCO - learn more)

Fixes # #6153

Relates to #

[SpiritZhou]

Could you also add some e2e tests?

[BojanZelic]

@SpiritZhou I fixed the PR from your comments and updated the helmchart & documentation 🙏 please take a look whenever you get a chance.

[SpiritZhou]

/run-e2e hashicorp
Update: You can check the progress here

[JorTurFer]

LGTM! The only point I have is the one related with the other PR adding support for the same API for other usage

[wozniakjan]

lgtm, thank you!

[wozniakjan]

/run-e2e secret
Update: You can check the progress here

[BojanZelic]

@wozniakjan I had a file rename as part of the PR that shouldn't have been there (fixed in f414b39 ) and the e2e tests were failing, I think they should be good now 🤞

[wozniakjan]

/run-e2e hashicorp_vault
Update: You can check the progress here

[BojanZelic]

@zroubalik any thoughts for getting this PR merged?

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed in 7 days if no further activity occurs. Thank you for your contributions.

[rickbrouwer]

/run-e2e hashicorp_vault
Update: You can check the progress here

[zroubalik]

Once docs PR is resolved, we can merge.

Thanks!

[rickbrouwer]

/run-e2e hashicorp_vault
Update: You can check the progress here

[rickbrouwer]

Hi @BojanZelic , i see there is a merge conflict

[wozniakjan]

/run-e2e hashicorp_vault
Update: You can check the progress here