Sergey Vasilyev

Usually, the object is a plain dict. It can be modified. ```python kopf.adopt(...) for ref in data['metadata']['ownerReferences']: ref['controller'] = False ``` `kopf.adopt()` is supposed to take full ownership of the...

Sorry for the late response (just noticed the question). I'd suggest using labels to mark the parent-children relationships: You can use the `patch` kwarg to directly decide what to store...

There is no such option, sadly. But you can always create your own fine-tuned webhook configuration manually and disable the auto-management in Kopf. The configuration auto-management is supposed to be...

Sorry, I didn't get the setup. A code snippet can be helpful here. If you meant 2 decorators for the same function, you can try using handler parametrisation: https://kopf.readthedocs.io/en/stable/kwargs/?highlight=param#std-kwarg-param

> Operator resumes the on.create handler if there is a pod restart, right? Well, as far as I know, no. If the pod is restarted, it is the same pod,...

Generally, you cannot. It is not related to Kopf, it is how Kubernetes behaves: once a resource is marked for deletion (by setting its `.metadata.deletionTimestamp`), it cannot be un-marked. I...

Thanks for this PR and for your time spent on it. However, I think, I will not merge it — but for a good cause: While playing with two separate...

Hello. Thanks for this proposal. Truth be told, I never used Helm, only read the docs, so I do not know what is the best way to organise charts and...

Hello. Yes, a code snippet might help. The logs with `-v` (verbose mode) will be helpful too. My current suspicion is that the namespace deletion stops the namespace watcher task....

Hello. > … if I understand correctly is extracting the token only at startup and then continue to use it over the lifetime of the pod. Not exactly. The behaviour...