disable service sync with yaml and consume service remotely

examples/no-ingress.yaml

@@ -5,3 +5,4 @@ metadata:
 data:
   name: my-site
   ingress: "none"
+  service-sync: "false"

yaml/annotations.adoc

@@ -136,3 +136,39 @@ Applies to:
 // Applies to:
 // * StatefulSets
 
+
+// Type: procedure
+[id="service-yaml"] 
+= Creating a service when service-sync is disabled
+
+If you set `service-sync: "false"` when creating a site and you want to consume a service exposed on another site:
+
+. Create `backend.yaml` similar to the following:
++
+[source, yaml]
+----
+apiVersion: v1
+kind: Service
+metadata:
+  name: backend
+  annotations:
+    skupper.io/proxy: tcp
+    skupper.io/address: backend
+    skupper.io/port: "8080"
+    skupper.io/ingress-only: "true"
+spec:
+  ports:
+    - name: http
+      protocol: TCP
+      port: 8080
+      targetPort: 8080
+----
+
+. Apply that yaml in the context of the site where `service-sync` is disabled:
++
+[source, yaml]
+----
+$ kubectl apply -f backend.yaml
+----
+
+. Test the service.

yaml/index.adoc

@@ -82,12 +82,16 @@ include::../examples/my-site.yaml[]
 ----
 The YAML creates a site with a console and you can create tokens from this site.
 
-To create a site that has no ingress:
+To create a site that has no ingress and with `service-sync` disabled:
 
 ----
 include::../examples/no-ingress.yaml[]
 ----
 
+NOTE: By default, `service-sync` is enabled and if you create a service on one site, it is available on all sites.
+If `service-sync` is set to false for a site, you need to create the service on that site as described in xref:service-yaml[].
+
+
 --
 . Apply the YAML file to your cluster:
 +
@@ -171,8 +175,6 @@ A future release of Skupper will provide an alternative declarative method to cr
 
 include::annotations.adoc[leveloffset=+1]
 
-
-
 // Type: reference
 [id="site-config-reference"] 
 [appendix]