This allows a site to target pods in other namespaces. It adds two new resource types. The AttachedConnector resource is declared in the namespace where the pods to be tracked are running. It is largely similar to the Connector resource, but has a siteNamespace field that identifies the site in which it is desired that the pods being tracked are used to configure connectors. The other new resource type is the AttachedConnectorAnchor. This is created in the namespace of the site for which an AttachedConnector is to be defined.
To track pods in another namespace, a pair of resources, one of each of these new types is required. These should use the same resource name. The AttachedConnector is defined in the namespace where the pods to be tracked are running. The AttachedConnectorAnchor is defined in the site that should be targetting those pods. This way, RBAC can be used to ensure that appropriate access to each namespace is required (not necessarily by the same person) in order for a site to be able to track pods in another namespace. Each of the resources in the pair references the namespace of the other. In the case of the AtttachedConnector, this is done through the siteConnector field. In the case of the AttachedConnectorAnchor, this is done through the connectorNamespace field.
This allows a site to target pods in other namespaces. It adds two new resource types. The AttachedConnector resource is declared in the namespace where the pods to be tracked are running. It is largely similar to the Connector resource, but has a siteNamespace field that identifies the site in which it is desired that the pods being tracked are used to configure connectors. The other new resource type is the AttachedConnectorAnchor. This is created in the namespace of the site for which an AttachedConnector is to be defined.
To track pods in another namespace, a pair of resources, one of each of these new types is required. These should use the same resource name. The AttachedConnector is defined in the namespace where the pods to be tracked are running. The AttachedConnectorAnchor is defined in the site that should be targetting those pods. This way, RBAC can be used to ensure that appropriate access to each namespace is required (not necessarily by the same person) in order for a site to be able to track pods in another namespace. Each of the resources in the pair references the namespace of the other. In the case of the AtttachedConnector, this is done through the siteConnector field. In the case of the AttachedConnectorAnchor, this is done through the connectorNamespace field.