external-secrets/kubernetes-external-secrets

KES is deprecated, migrate to ESO!

Flydiverny opened this issue ยท 11 comments

Hi! ๐Ÿ‘‹

KES is officially deprecated

Are you a new user looking to start using KES?
Please take a look at the ESO instead!

KES = Kubernetes External Secrets (this repo)
ESO = External Secrets Operator (repo: external-secrets/external-secrets)

KES is under limited maintenance and the go rewrite ESO has come a long way and more than likely covers your use case, while doing it better at the same time. If it doesn't please raise an issue over there or even better contribute!

ESO offers better documentation, better configuration possibilities, uses modern dependencies, and is written in kubernetes community friendly Golang ๐Ÿ˜„

ESO can be found here:

KES does not have any dedicated or active maintainer at this time and is on limited life support (and has been for awhile).
As can be seen from some issues, there are tech debts in this project that are causing issues and some of the dependencies we depend on are no longer maintained. To replace them would have required a sizeable effort and is hard to motivate with the golang rewrite ESO having come a long way!

If you have any questions or so feel free to join the community over at #external-secrets in the Kubernetes slack!

This is an acceptable solution to my issues. While it's annoying to have to replace the KES engine, this new project looks promising.

thanks!

There's a tool WIP to ease migration path:
https://github.com/external-secrets/kes-to-eso
But I think most of it is still in a PR external-secrets/kes-to-eso#1 but we'd love help testing it!

I think a deprecation notice on the main README is needed :)
#905

Would love to have the deprecation notice on artifact hub: https://artifacthub.io/packages/helm/external-secrets/kubernetes-external-secrets

Would love to have the deprecation notice on artifact hub: artifacthub.io/packages/helm/external-secrets/kubernetes-external-secrets

Should be fixed in 8.5.3 might take awhile before it shows up on artifacthub tho

Ah, there it is! Thank you! ๐Ÿ˜

cep21 commented

Hi,

The new repo is still at v0.x

When is it safe to migrate production deployments over? Are there plans for a 1.0 release?

Hi,

The new repo is still at v0.x

When is it safe to migrate production deployments over? Are there plans for a 1.0 release?

Hi @cep21 ! Even though our release are still at v0.x, most of the providers are already graded stable. We are currently still in a v0.x mostly because our CRDs are still in alpha. We are aiming to release stable CRDs (and therefore a 1.0 release) by the end of this year.

I would still encourage you to see ESO nevertheless. As I already stated before, the reconciliation mechanism for most of the providers are considered stable (with a significant amount of e2e testing being ran against them).

Thank you very much for all your help and dedication at KES @Flydiverny

Can this project be marked read-only/archived? I keep ending up on it from google, and seeing recent bot commit history doesn't help to disambiguate it from the active project.
Thanks!

@grrttedwards I suppose its time now!

Marking repo as archived, as of now :)