Support for built-in resources (pods, jobs, etc) about kopf HOT 3 CLOSED

Quick-check results:

It might look like a good idea to use CustomObjectsApi() for the built-in resources too, e.g. @kopf.on.event('', 'v1', 'pods') — as an expected semantics. Sadly so, the resulting URLs are different:

Built-in V1 pods URL: /api/v1/namespaces/default/pods
Via custom resources: /apis//v1/namespaces/default/pods

First of all, the /api vs /apis is a problem, which leads to "404 Not Found".
Second, the double-slash // is a problem, it also returns "404 Not Found" (event with /api/).
When both of these are hacked, it works as expected.

The URL parts are quoted, so it is impossible to do anything like @kopf.on.event('../api', 'v1', 'pods'), as the resulting URL becomes /apis/..%2Fapi/v1/namespaces/default/pods.

Which means, there is no easy hack in Kopf itself to get to the built-in resources with the official client with all the hard-coded URLs. Runtime monkey-patching of the client library might be a bad idea for the stability of the Kopf-based operators that use this library.

So, the choice is either to map every known builtin resource to proper classes&methods, which means making Kopf into a Kubernetes client library (which is not the framework's mission), or using another Kubernetes client with dynamic mapping of any resources, builtin and custom, via the same interface.

from kopf.

This is actually solved in #15 as a side-effect (but needs to be merged first).

from kopf.

@nolar is there an example of watching a pod under a parent crd? I noticed you sketched ideas in several issues, but I'm not sure which you ended up on.

from kopf.