-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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 source.Kind for unstructured objects #17
Comments
I am interested in helping with this issue. I was wondering if you had thoughts on how to handle this already or if a design doc or something similar has been created? |
@shawn-hurley Not yet, though I think the interface shouldn't change, it should just accept unstructured objects. Would you be willing to put together a 1-2 page doc on the topic before getting started? From a high level:
One question is whether the cache should be shared between unstructured and hard-coded objects for the same GVK. As long as it is consistent and predictable I think either way is good. |
@shawn-hurley FWIW, this might already work. I think the first task is to try it and see if it works or not, then dig in deeper. |
@pwittrock I think that it would work with a single unstructured type, but if you used two then the client-cache: https://github.com/kubernetes-sigs/controller-runtime/blob/master/pkg/client/client_cache.go#L79-L84 will overwrite the GVK for one fo the types. Am I correct in that reading of the code? I will work on getting an example to test this theory as well. Thanks! |
aah, yeah, we probably would need a key that's like |
or have a separate map for unstructured objects. |
@pwittrock @DirectXMan12 I am working on getting an example of using two different unstructured types to test this theory out and to have something to test with. Which would you prefer the second map if the type is Unstructured or some other mechanism? I would think that two maps might make it more clear? |
Two maps is probably clearer. |
Improve compile message from run
We should be able to watch for objects against unstructured objects from source.Kind.
The text was updated successfully, but these errors were encountered: