Skip to content

Commit 02daa80

Browse files
committed
wording in docs
On-behalf-of: @SAP [email protected]
1 parent 45e21fc commit 02daa80

File tree

1 file changed

+3
-3
lines changed

1 file changed

+3
-3
lines changed

docs/content/publish-resources/related-resources.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -27,9 +27,9 @@ Related resources can be
2727
For each related resource, the Sync Agent needs to be told how to find the object on the origin side
2828
and where to create it on the destination side. There are multiple options that you can choose from.
2929

30-
By default all related objects live in the same namespace as the primary object (their owner/parent).
31-
If the primary object is cluster scoped, admins must configure additional rules to specify what
32-
namespace the ConfigMap/Secret shall be read from and created in.
30+
By default all related cobjects live in the same namespace as the primary object (their owner/parent).
31+
If the primary object is cluster scoped, a namespace must be configured to specify which namespaces
32+
the resource shall be read from and written to.
3333

3434
Related resources are always optional. Even if references (see below) are used and their path
3535
expression points to a non-existing field in the primary object (e.g. `spec.secretName` is configured,

0 commit comments

Comments
 (0)