Secret-Manager docs are, ahem, limited.
I've used both solutions, and ultimately, I think itscontained/secret-manager is better than external-secrets.
Their doc was re-jiggled a few days ago and I agree its made it look like it's inexistant. There's not a _ton_ of it, but it's there[0][1]
[0]https://github.com/itscontained/secret-manager/tree/master/d...
[1]https://github.com/itscontained/secret-manager/blob/master/d...
edit: found the link in the Godaddy repo to "secret-manager": https://github.com/godaddy/kubernetes-external-secrets/issue...
I was mistaken when I said "secret-manager supplanted external-secrets". It's a Golang rewrite from a user.
There has been talks of moving one of these solutions to https://github.com/external-secrets ownership, but nothing has happened around that yet.
I've been using Secret-Manager and it works very well.
The authors of "kube-secret-syncer" mention "[other solutions] lack either in security, caching or flexibility".
When it comes to "secret-manager", although I can not vouch for its security, the codebase is very small and probably easily auditable.
It's also very flexible. It supports "SecretStores", currently AWS, GCP and Vault out of the box, and it's easy to add more.
Not sure why "caching" is mentioned in the mix.
I'm surprised they decided to re-invent the wheel instead of improving secret-manager.
[0]: https://github.com/godaddy/kubernetes-external-secrets
[1]: https://github.com/itscontained/secret-manager