summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorKubernetes Prow Robot <k8s-ci-robot@users.noreply.github.com>2021-07-09 10:54:53 -0700
committerGitHub <noreply@github.com>2021-07-09 10:54:53 -0700
commita843caa9b14a54232a08012693367cc52c583b30 (patch)
treebff72c9762c9a224b9c72ae462f898d8ddd5aaa9
parentbbf6ceb1eb6e8c30cf5fb8c255995a2b953f75c1 (diff)
parent00d73216d377870f851a07dddef0bbe6265ad593 (diff)
Merge pull request #5832 from toumorokoshi/feature/consolidate-object-reference-guidance
consolidate object ref guidance in api conventions
-rw-r--r--contributors/devel/sig-architecture/api-conventions.md9
1 files changed, 4 insertions, 5 deletions
diff --git a/contributors/devel/sig-architecture/api-conventions.md b/contributors/devel/sig-architecture/api-conventions.md
index 5d0b1eab..30bee638 100644
--- a/contributors/devel/sig-architecture/api-conventions.md
+++ b/contributors/devel/sig-architecture/api-conventions.md
@@ -479,11 +479,7 @@ ensure that GETs of individual objects remain bounded in time and space, these
sets may be queried via separate API queries, but will not be expanded in the
referring object's status.
-References to specific objects, especially specific resource versions and/or
-specific fields of those objects, are specified using the `ObjectReference` type
-(or other types representing strict subsets of it). Unlike partial URLs, the
-ObjectReference type facilitates flexible defaulting of fields from the
-referring object or other contextual information.
+For references to specific objects, see [Object references](#object-references).
References in the status of the referee to the referrer may be permitted, when
the references are one-to-one and do not need to be frequently updated,
@@ -906,6 +902,9 @@ It is okay to have the "{field}" component indicate the resource type. For examp
a secret. However, this comes with the risk of the field being a misnomer in the case that the field is expanded to
reference more than one type.
+In the case of a list of object references, the field should be of the format "{field}Refs", with the same guidance
+as the singular case above.
+
### Referencing resources with multiple versions
Most resources will have multiple versions. For example, core resources