-
Notifications
You must be signed in to change notification settings - Fork 788
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
migrate from KES to ESO #8298
Comments
Starting the work this weekend, will update this issue with any progress/roadblock. |
Any branch I can follow yet? |
Excited to see some progress on this! 🤞 |
Any progress on this? Is it possible to plug the new Secrets provider into JX or will it break the setup/not work at the moment? |
@ankitm123 is this a lot harder than you initially thought or something? |
Too bad this project is becoming so stale :-( |
Hey @lodotek, we can support you developing this feature if it's something that you'd like to do 👍 |
Any update on this? Not an expert in this, but if we can help, we would like to offer some time. |
any update ? |
i see 2 existing PRs |
Hey @joshuasimon-taulia, 397 is my pr, I was doing a full boot job conversion, changing jx secret so that we could essentially scream test and see what breaks. Ankits pr seems to already approach what he knew would break. I started again originally because I found it hard to pickup where Ankit left off. If you decide with 397, The main thing that I needed to do next was to update all of the tests. From KES to ESO, it seems that the structure of the secrets has changed very little, it's more about updating the tests, I think that you'll probably want to write a little go script to automatically go through and update the tests (because there is a lot of them) and I don't want you to waste your time doing it manually. There's a couple of changes that I wanted to make, one of the big ones was making the secret generation generate a space in vault that meant that the secrets had the environment included within the path, otherwise all of the resources across the namespace share one secret (which isn't ideal) |
KES is in maintaince mode, and we should move to ESO instead
external-secrets/kubernetes-external-secrets#864
The text was updated successfully, but these errors were encountered: