AttachedConnector example uses inconsistent site namespaces

[pwright]

Description

The attached connector example in the Kubernetes YAML service-exposure documentation uses different namespaces for the site:

• AttachedConnector.spec.siteNamespace is set to skupper.
• The associated AttachedConnectorBinding is created in namespace east.

siteNamespace must identify the namespace containing the Skupper site and the associated AttachedConnectorBinding. As written, the two resources do not form a valid pair.

Location

• Published documentation: https://skupper.io/docs/kube-yaml/service-exposure.html#creating-a-connector-for-a-different-namespace-using-yaml
• Source: input/kube-yaml/service-exposure.md

Current example

apiVersion: skupper.io/v2alpha1
kind: AttachedConnector
metadata:
  name: backend
  namespace: attached
spec:
  siteNamespace: skupper
  selector: app=backend
  port: 8080
---
apiVersion: skupper.io/v2alpha1
kind: AttachedConnectorBinding
metadata:
  name: backend
  namespace: east
spec:
  connectorNamespace: attached
  routingKey: backend

Expected example

Assuming that the site is in namespace east, change siteNamespace to east:

apiVersion: skupper.io/v2alpha1
kind: AttachedConnector
metadata:
  name: backend
  namespace: attached
spec:
  siteNamespace: east
  selector: app=backend
  port: 8080
---
apiVersion: skupper.io/v2alpha1
kind: AttachedConnectorBinding
metadata:
  name: backend
  namespace: east
spec:
  connectorNamespace: attached
  routingKey: backend

Additional documentation fixes

• Replace the link to the Connector resource with links to the AttachedConnector and AttachedConnectorBinding resource references.
• Create the attached namespace in the procedure, or list it as a prerequisite, before running the deployment command with --namespace attached.