clarify subresource handling

On-behalf-of: @SAP [email protected]

Author: xrstf

docs/content/faq.md

@@ -42,7 +42,7 @@ to the APIExport it manages:
   be any resource)
 
 The syncagent will always overwrite the entire list of permission claims, i.e. you cannot have custom
-claims in an APIExport.
+claims in an APIExport managed by the api-syncagent.
 
 ## I am seeing errors in the agent logs, what's going on?
 

internal/sync/syncer_related.go

@@ -143,12 +143,17 @@ func (s *ResourceSyncer) processRelatedResource(ctx context.Context, log *zap.Su
 
 				return dest, nil
 			},
-			// reloated resources have no subresources
+			// Originally related resources were only ConfigMaps and Secrets, which do not have subresources;
+			// nowadays we support arbitrary APIs for related resources, but for simplicity do not [yet?]
+			// support syncing the subresources back. For this we would first need to figure out which
+			// subresources even exist.
 			subresources: nil,
-			// only sync the status back if the object originates in kcp,
-			// as the service side should never have to rely on new status infos coming
-			// from the kcp side
-			syncStatusBack: relRes.Origin == "kcp",
+			// Theoretically we would only want to sync the status back if the related resource
+			// originates in kcp, because it would be weird if the service provider relied on status
+			// information provided to them by the consumer.
+			// However since we do not know anything about subresources, we currently cannot enable this
+			// feature at all.
+			syncStatusBack: false,
 			// if the origin is on the remote side, we want to add a finalizer to make
 			// sure we can clean up properly
 			blockSourceDeletion: relRes.Origin == "kcp",