Service Fabric Mesh is the Service Fabric's serverless offering to enable developers to deploy containerized applications without managing infrastructure. Service Fabric Mesh , aka project “SeaBreeze” is currently available in private preview. This repository will be used for tracking bugs/feature requests as GitHub issues and for maintaining the latest documentation.
Networks are individually deployable resources, just like applications and services. A network resource is used to create a private network for your applications. Multiple services from different applications can be part of the same network.
Things that I'm wondering about:
How does one create an internal-only network?
Omitting the ingressConfig results in a failure from what I've noticed
Can we mix public ports and internal ports?
Can I use port-forwarding for cross-application communication or will this only be supported with Envoy?
Do I need to specify an addressPrefix? This is a PaaS product so why should I bother about this to a certain degree?
Will anything else be supported other than ingressConfig.layer4?
What is ingressConfig.qosLevel and will this be removed given this is probably referring to the cluster node tier?
Are there plans to provide more documentation on the networking aspect of Mesh?
Currently the only documentation that I can find is:
Things that I'm wondering about:
ingressConfigresults in a failure from what I've noticedaddressPrefix? This is a PaaS product so why should I bother about this to a certain degree?ingressConfig.layer4?ingressConfig.qosLeveland will this be removed given this is probably referring to the cluster node tier?