No. The notion of a Raft leader belongs to Cluster internals. To the outside, every peer is the same.
The problem is the same as for every peer 2 peer application and not cluster-specific. Cluster, like ipfs, uses libp2p. If connections cannot cross NATs things won’t work. We are tracking some efforts here https://github.com/ipfs/ipfs-cluster/issues/614
Private networks is a libp2p feature that wraps encrypts all libp2p traffic with an additional pre-shared-key. It does not create network interfaces. It just prevents any meaninful communication to happen with peers not configured with that pre-shared key.
Mixing with Textile seems to do the job of asking remote pinning
I have configured a node as a gateway (one of the all pinning node).
As files are added and CID changed everytime, using ipfs name publish <New_CID> should update gateway URL.
Do I need subpub or something like it to sync “LinkDNS” changes?