Skip to content
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

[feature request] support kubernetes-external-secrets #100

Open
sonots opened this issue Nov 27, 2020 · 1 comment
Open

[feature request] support kubernetes-external-secrets #100

sonots opened this issue Nov 27, 2020 · 1 comment

Comments

@sonots
Copy link

sonots commented Nov 27, 2020

I am using https://github.com/external-secrets/kubernetes-external-secrets to manage secrets via AWS Secrets Manager.

Do you have any plans to support such custom resources with this plugin?
I am glad if external-secrets will also be supported (and also thinking about forking this plugin to support external-secrets if not planned).

@micnncim
Copy link
Owner

micnncim commented Nov 28, 2020

Yes, I'm planning that.

I'm thinking of how kubectl-reap should support custom resources. As you know, there a lot of custom resources. Therefore, it'd be unrealistic that I implement support of each custom resource every time someone wants. As one of ideas, it might be good to implement a plugin system to support custom resources, with which users fork this repository, then could easily implement support of the custom resources they are using, and perhaps could submit a PR of the implementation to this repository if it'd be useful for others.

However, I've not fixed any design yet and the implementation wouldn't come soon. Once I implement it, I'm going to make support of popular custom resources like ExternalSecret. If you want the support soon, I recommend you this repository and then use the forked one. I'd appreciate your any kind of contribution 😄

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants