-
Notifications
You must be signed in to change notification settings - Fork 55
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
OpenShift.clean() does not clean custom resources #293
Comments
It's possible to work with |
Could you reference some example of working with |
Some examples can be found in Working with CustomResourceDefinitions The first approach with POJOs: The newer API levering raw approach without POJOs: AFAIK, there's no definitive and good answer from client devs. They're working on simplifying the whole process. Anyway the former approach required to define POJOs for In Kafka Operator (Java based operator) they do generate class model the same way as in IMO the raw approach seems a bit more promising and easier to impl/maintain, but I haven't tried it yet. Anyway I don't think we can/should add a direct support to XTF for any of the specific CRDs, CRs. That'd make it even more obscure to work with. |
It should be possible to use a dynamic client (just for deletion), as you don't have to know anything about the CRDs to delete its CRs. You only need to know the Group, Version and Resource to get the list of CRs and to delete them. (so we could have something like
To have clean delete all "all"s, it would only have to list all CRDs that list "all" as its category.. (note that it doesn't necessary mean "all CRDs that exist") , not sure if "oc" use some special API for it (as apparently it knows the list even if the user cannot list CRDs... ) |
Resolved by #299. Closing. |
I mean we are testing operator which introduce resource api
WildFlyServer.wildfly.org
. Of course xtf has no idea of such resource.Now what are options to resolve this? Provide method, such caller can specify additional resources he wants to remove?
Or take another approach similar to
oc --loglevel=10 delete all --all
. Which seems first take available resource apis and then for each tries to remove resources. (but I have no idea how that can be implemented)The text was updated successfully, but these errors were encountered: