Feature: multiple backend in the same external secret about kubernetes-external-secrets

[Flydiverny]

Is there really a use case for this though? I mean is there any case where it would end up being an actual problem to create an additional external secret? Seems like a good way to handle it, I'd expect most uses to stick to the same backend type throughout unless migrating from one secret storage to another.

[Sytten]

I don't exactly remember the use case since I don't work at the same company anymore, but I feel you might want some information in SM (databases creds for example to use rotation), but most of the stuff in SSM since you have to pay for it.

[DWSR]

This is something we'd be very interested in as we currently use HashiVault and SSM Parameter Store for secrets. Using multiple backends enables an easier transition between secret backends and also enables us to avoid duplicating secrets amongst the various backends.

[github-actions]

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.

[Sytten]

Not stale

[github-actions]

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.

[Sytten]

Not stale

[Flydiverny]

This will not be added to KES.
Neither has it been included in the CRD spec we came up with for ESO. I think the best thing now would be to make a feature request on the rewrite instead.