diff options
| author | Kubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com> | 2021-04-06 07:33:33 -0700 |
|---|---|---|
| committer | GitHub <noreply@github.com> | 2021-04-06 07:33:33 -0700 |
| commit | 0b9dbc303a6bcc182a4353a7fbc7ab6f69a1bb61 (patch) | |
| tree | 2aa01117229a8c60bb9e43c68deae29f3b033a8d | |
| parent | 346e7d48cf3bded807e44f38801e35012c71ce8b (diff) | |
| parent | 27e1a810294b76b80d7258ca3fe5a9096f070cf8 (diff) | |
Merge pull request #5695 from apelisse/add-documentation-api-conventions
Include documentation for listTypes in api conventions
| -rw-r--r-- | contributors/devel/sig-architecture/api-conventions.md | 9 |
1 files changed, 6 insertions, 3 deletions
diff --git a/contributors/devel/sig-architecture/api-conventions.md b/contributors/devel/sig-architecture/api-conventions.md index 7be33259..68f304c9 100644 --- a/contributors/devel/sig-architecture/api-conventions.md +++ b/contributors/devel/sig-architecture/api-conventions.md @@ -491,9 +491,12 @@ particularly in an edge-based manner. #### Lists of named subobjects preferred over maps -Discussed in [#2004](http://issue.k8s.io/2004) and elsewhere. There are no maps -of subobjects in any API objects. Instead, the convention is to use a list of -subobjects containing name fields. +Discussed in [#2004](http://issue.k8s.io/2004) and elsewhere. There are +no maps of subobjects in any API objects. Instead, the convention is to +use a list of subobjects containing name fields. These conventions, and +how one can change the semantics of lists, structs and maps are +described in more details in the Kubernetes +[documentation](https://kubernetes.io/docs/reference/using-api/server-side-apply/#merge-strategy). For example: |