disable service sync with yaml and consume service remotely #257
Conversation
* tls concepts
* update link-cost
|
@sjhiggs could you take a look? |
pwright
changed the title
|
@hash-d Could you take a look? The idea is to document
|
|
|
||
| ---- | ||
| 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. |
There was a problem hiding this comment.
I'm not sure about using 'available' here. The skupper service is still available on all sites. The difference is that without the service-sync a k8s service will not be automatically created on this site.
Perhaps something along the lines
By default
service-syncis enabled, and a Kubernetes service is automatically created locally for each/every/all skupper services present on the VAN
| - name: http | ||
| protocol: TCP | ||
| port: 8080 | ||
| targetPort: 8080 |
There was a problem hiding this comment.
There are three places where 'port' is set; it might be interesting to explain what's the role of each of them, especially given that one of them will be overwritten by Skupper.
| name: backend | ||
| annotations: | ||
| skupper.io/proxy: tcp | ||
| skupper.io/address: backend |
There was a problem hiding this comment.
It may be interesting to mention that this needs to match the name of the service created on the other side, as that will be the main alteration the user will do on this file.
No description provided.