You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Copy file name to clipboardExpand all lines: docs/book/src/reference/owner_references.md
+42-40Lines changed: 42 additions & 40 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -16,65 +16,67 @@ CAPI uses owner references in an opinionated way. The following guidelines shoul
16
16
17
17
## Owner reference relationships in Cluster API
18
18
19
-
The below tables map out the a reference for ownership relationships for the objects in a Cluster API cluster.
19
+
The below tables map out the a reference for ownership relationships for the objects in a Cluster API cluster. The tables are identical for classy and non-classy clusters.
20
+
21
+
20
22
Providers may implement their own ownership relationships which may or may not map directly to the below tables.
21
23
These owner references are almost all tested in an [end-to-end test](https://github.com/kubernetes-sigs/cluster-api/blob/caaa74482b51fae777334cd7a29595da1c06481e/test/e2e/quick_start_test.go#L31). Lack of testing is noted where this is not the case. CAPI Providers can take advantage of the e2e test framework to ensure their owner references are predictable, documented and stable.
0 commit comments