-
I'm trying to manage some resources that can be very large - - more than the 262144 bytes allowed in annotations for the last-changed-config, so I'm getting 422 Unprocessable Entity errors when kopf tries to update the resource status.
Is there a solution/workaround other than server-side-apply, which seems like a lot of work to implement? Thanks |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments
-
You can implement your own state & progress key-value storages (see the docs), e.g. in sqlite/postgres/mysql, or in a shared filesystem with json in files. Or you can configure the pre-implemented storages in the status field (also documented). The annotation storages are made a default to serve builtin resources (like pods) out of the box, since the builtins prohibit writing arbitrary data to their status. The same can be expected for crds unless their schema allows such storage. |
Beta Was this translation helpful? Give feedback.
-
Thanks @nolar - that worked. For reference this is what I used:
I have |
Beta Was this translation helpful? Give feedback.
You can implement your own state & progress key-value storages (see the docs), e.g. in sqlite/postgres/mysql, or in a shared filesystem with json in files.
Or you can configure the pre-implemented storages in the status field (also documented).
The annotation storages are made a default to serve builtin resources (like pods) out of the box, since the builtins prohibit writing arbitrary data to their status. The same can be expected for crds unless their schema allows such storage.