-
Notifications
You must be signed in to change notification settings - Fork 359
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
fix: Kubernetes External Secrets deprecated, replaced by External Secrets Operator #3661
base: main
Are you sure you want to change the base?
Conversation
Kudos, SonarCloud Quality Gate passed! |
Hi @ned-si. Thanks for your PR. I'm waiting for a jenkins-x or todo member to verify that this patch is reasonable to test. If it is, they should reply with Once the patch is verified, the new status will be reflected by the I understand the commands that are listed here. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the jenkins-x/lighthouse repository. |
[APPROVALNOTIFIER] This PR is NOT APPROVED This pull-request has been approved by: The full list of commands accepted by this bot can be found here.
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
Not yet, it's still a work in progress. I will add a comment here, once it's working. |
/hold |
@ankitm123 can you elaborate? What's "still a work in progress"? ESO integration? The PR changes docs that are already live on your website and in their current form refer to the deprecated tool. |
Jenkins X still uses KES and not ESO. This is still being worked on: jenkins-x-plugins/jx-secret#387 |
Description
The project Kubernetes External Secrets is deprecated and has been replaced by External Secrets Operator. Jenkins X is using the right one, but the documentation was still mentioning the old one. It has been fixed everywhere, except in the blog posts (intentionally).
Fixes # (issue)
Checklist: