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

Add support for CustomResourceDefinitions (and phase out TPRs) #25

Closed
luxas opened this issue Aug 7, 2017 · 12 comments
Closed

Add support for CustomResourceDefinitions (and phase out TPRs) #25

luxas opened this issue Aug 7, 2017 · 12 comments
Assignees
Labels
kind/bug Behavior isn't as expected or intended lifecycle/active Actively being worked on p2-moderate

Comments

@luxas
Copy link

luxas commented Aug 7, 2017

As you all know, CRDs are the successor of TPRs.
TPRs will be removed in v1.8, make sure sonobuoy can handle that gracefully ;)

@timothysc timothysc self-assigned this Aug 7, 2017
@timothysc timothysc added kind/bug Behavior isn't as expected or intended p1-important labels Aug 7, 2017
@timothysc timothysc added this to the v0.9.0 milestone Aug 7, 2017
@timothysc
Copy link
Contributor

Yup, this is known. We just wanted to get it out and I'll update soon-ish.

@timothysc
Copy link
Contributor

I will also need to update the deps on this one.

@kensimon
Copy link

Thoughts:

CRDs aren't a part of client-go yet, you need to initialize a separate clientset for everything under apiextensions. It seems like it will eventually be rolled in, see: kubernetes/client-go#247

We can refactor pretty heavily to ensure the clientset and the apiextensions clientset are both passed around to the various discovery functions, or we can wait for the above issue to be addressed (and maybe help with it.)

@timothysc
Copy link
Contributor

We should wait until CRDs are in client-go.

Blarg, I want to avoid the vendor nightmare that we pulled before. Perhaps we should poke @ncdc on this issue.

@ncdc
Copy link
Contributor

ncdc commented Sep 5, 2017

@kensimon @timothysc I'm not sure what you mean about CRDs not being in client-go? Are you talking specifically about having a typed client to be able to register CRDs? If so, then you're correct, that's part of apiextensions. But we've stated that we'll ship CRDs as yaml and require admins to install them via kubectl. Or are you talking about something slightly different?

@timothysc
Copy link
Contributor

@ncdc this is about scanning and reporting what is there for diagnostics and reporting.

@ncdc
Copy link
Contributor

ncdc commented Sep 5, 2017

I see. I would vendor in what you need from apiextensions for now, or if that's too painful, just build your own client.

@timothysc
Copy link
Contributor

This is pending an updated to client... on hold blocked atm.

@timothysc timothysc added the lifecycle/blocked Progress can't continue on this issue label Sep 7, 2017
@timothysc timothysc added lifecycle/active Actively being worked on and removed lifecycle/blocked Progress can't continue on this issue labels Sep 25, 2017
@timothysc
Copy link
Contributor

This is now unblocked, I'll have a fix soonish.

@timothysc
Copy link
Contributor

This may be a push b/c client-go doesn't actually have the straight up interface that I'm looking for, but exists in the main repository.

client.Apiextensions().CustomResourceDefinitions().List(options)

which is essentially under the ApiextensionsV1beta1 group is nowhere to be found in the client, but I'm sure could be accessed through discovery.

@timothysc
Copy link
Contributor

It requires a separate client util+wrapper k8s.io/apiextensions-apiserver which is outside of client-go.

@luxas
Copy link
Author

luxas commented Oct 6, 2017

Thanks for fixing this @timothysc!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Behavior isn't as expected or intended lifecycle/active Actively being worked on p2-moderate
Projects
None yet
Development

No branches or pull requests

4 participants