kopf

Problem

K8s-event posting can fail to post an event (kind: Event) for any reasons, such as API rate limiting, temporary API failures (HTTP 5xx), control plane connectivity issues, SSL handshake failures, etc.

This leads to the events being lost, while they can represent some value. This applies both to the events created from the per-object logger messages (logger.info(...) from the

Read only fields were meant to be read only. However sometimes these fields must be set (in the case of an operator managing these resources for example).

We should add a mean to edit these fields with a context manager for example:

with pykorm.fields.UnlockReadOnly:
  obj.read_only = 42

While the code provides the full CustomResourceDefinition the documentation is lacking clear examples of what is possible and what not. E.g. a very simple custom resource with only the required arguments, a more advanced one that shows some possibilities, and a complex one, making use of all available options.