From cd04d3ff716c4fe11cc6f2355c861bebd3097a6b Mon Sep 17 00:00:00 2001 From: Nikhita Raghunath Date: Wed, 5 Dec 2018 21:49:26 +0530 Subject: [PATCH] Fix references to patchMergeKey and patchStrategy in types.go (#11546) --- .../overview/object-management-kubectl/declarative-config.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md b/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md index 70fc566dfc..f2182e2bc1 100644 --- a/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md +++ b/content/en/docs/concepts/overview/object-management-kubectl/declarative-config.md @@ -625,7 +625,7 @@ Add, delete, or update individual elements. This does not preserve ordering. This merge strategy uses a special tag on each field called a `patchMergeKey`. The `patchMergeKey` is defined for each field in the Kubernetes source code: -[types.go](https://git.k8s.io/api/core/v1/types.go#L2565) +[types.go](https://github.com/kubernetes/api/blob/d04500c8c3dda9c980b668c57abc2ca61efcf5c4/core/v1/types.go#L2747) When merging a list of maps, the field specified as the `patchMergeKey` for a given element is used like a map key for that element. @@ -700,7 +700,7 @@ As of Kubernetes 1.5, merging lists of primitive elements is not supported. {{< note >}} Which of the above strategies is chosen for a given field is controlled by -the `patchStrategy` tag in [types.go](https://git.k8s.io/api/core/v1/types.go#L2565) +the `patchStrategy` tag in [types.go](https://github.com/kubernetes/api/blob/d04500c8c3dda9c980b668c57abc2ca61efcf5c4/core/v1/types.go#L2748) If no `patchStrategy` is specified for a field of type list, then the list is replaced. {{< /note >}}