Sergey Vasilyev

There will be another issue beside the annotations. Kopf stores its handlers' statuses in `.status.kopf.progress`, and purges the whole section once done regardless of the content. If multiple operators handle...

Hello. Thanks for reporting. This is not related to #231. This problem should be addressed by #55, and with the [admission validation hooks](https://kubernetes.io/docs/reference/access-authn-authz/extensible-admission-controllers/) in Kubernetes. As of now (Nov'2019), this...

Thank you for reporting it with all the details, especially with the packages. Can you please additionally `pip install kubernetes` — does it work then? --- Kopf contains only a...

Hm. That's interesting. What I see in the logs, is that pykube's credentials were retreived and didn't work: ``` [2020-04-21 17:42:45,962] kopf.reactor.activit [INFO ] Initial authentication has been initiated. [2020-04-21...

Kopf uses `pykube-ng` (which is a fork of `pykube`). Beside token-bearer, it also supports client certificate, username-password, and some other auth methods. At least, it is [in the code](https://github.com/hjacobs/pykube/blob/19.9.2/pykube/http.py#L128-L134). I...

_A little informational update:_ A normal non-hacky solution is coming soon. The work-in-progress code is already functional in my own fork, the examples are runnable, though there is no test...

@jicowan @Dmitry1987 The custom authentication methods were merged and released as `kopf==0.23rc1` (see the [release notes](https://github.com/zalando-incubator/kopf/releases/tag/0.23rc1) — there are many other changes). If the live testing goes well, it will...

Thanks for suggesting. Maybe namespace alone is not so special to be passed, but the whole CLI config can be packed into a single config-object, and passed to the startup/cleanup/login...

@eshepelyuk I would suggest to use 12-factor app-style configuration via env vars: pass a `NAMESPACE` (or `MYOP_NAMESPACE`) env var both to `--namespace=$NAMESPACE` and interpret it in your handlers via `os.environ['NAMESPACE']`....

The events' RBAC is fixed in #89 — the events API was changed from v1beta1 to core v1, but the docs were not in sync with that. For the `customresourcedefinitions`...