Skip to content
This repository has been archived by the owner on Oct 15, 2024. It is now read-only.

Commit

Permalink
decisions: clarify arbitrary metadata
Browse files Browse the repository at this point in the history
  • Loading branch information
Markus Raab committed Nov 9, 2020
1 parent 3c1c5bf commit aebd0eb
Showing 1 changed file with 6 additions and 1 deletion.
7 changes: 6 additions & 1 deletion doc/decisions/arbitrary_metadata.md
Original file line number Diff line number Diff line change
Expand Up @@ -23,7 +23,12 @@ metadata from `spec:` might end up in `user:`.

## Decision

Do not store metadata in any namespace but spec.
Do not store arbitrary metadata in any namespace but spec but only metadata that is handled by the `spec` plugin.
E.g. for `array`, metadata might be stored in any namespace but this does not present a problem:

- either the storage plugin does not support arrays, then the metadata will be discarded
- if the storage plugin supports arrays, the data will be serialized as array
(even if the metadata comes from `spec`)

Use different storage plugins, or plugins with different configurations,
for the `spec` namespace:
Expand Down

0 comments on commit aebd0eb

Please sign in to comment.