-
Notifications
You must be signed in to change notification settings - Fork 1.5k
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
Support for cert-manager model in fabric8 #2565
Comments
@PrakashNair : Umm, Could you please share the location of these cert-manager-model go structs? Maybe we can write a quick extension for these CRDS(like we have for Knative, Tekton, Istio etc) |
Thanks a lot for sharing! We can easily extend Kubernetes Client to create extensions. Writing an extension just involves these steps:
Would you like to contribute a PR in order to fix this? I think it would be awesome if we could get a contribution to this issue. You can check out these PRs to get an idea of how things are connected: ChaosMesh (Under Review) : #2556 |
/assign |
We don't have any bot for assigning issues 😆 . Thanks a lot for taking care of this issue. |
@rohanKanojia @arghya88 are you both still interested into supporting these CRDs? Do you need my contribution? |
I think we should definitely add support for this. ping @arghya88 Are you still working on this? |
@matthyx : Hi, Do you want to work on this issue? If you're busy, I can try picking this up in the next sprint. |
@rohanKanojia I have started to put the golang files into a branch... and see how they work. So nothing too advanced atm, but I can try to make it work for you :) |
@matthyx : Awesome, Thanks a lot!. Feel free to ping me on Gitter[0] in case you face problems with anything. |
Does the client library provide support for cert-manager CRDS (https://github.com/kubernetes-client/java/tree/master/client-java-contrib/cert-manager#cert-manager-model-classes)?
if yes, can you provide some pointers/examples on its usage? if no, are there any plans on extending the library to support it?
The text was updated successfully, but these errors were encountered: