You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We should introduce running the cluster in two modes:
public (default)
private
When an IPFSCluster resource runs in public network mode, pinned files are globally announced.
On the other hand, an IPFSCluster running in private mode will only be sharing files with itself across different nodes.
With the private mode, IPFSCluster is not very useful unless there are other IPFSCluster resources on other Kubernetes clusters which are able to reach them. Therefore, we want to be pulling in a secret via key reference and an IP4/IP6 address of the original IPFS Cluster peer
The text was updated successfully, but these errors were encountered:
We should introduce running the cluster in two modes:
When an IPFSCluster resource runs in public network mode, pinned files are globally announced.
On the other hand, an IPFSCluster running in private mode will only be sharing files with itself across different nodes.
With the private mode, IPFSCluster is not very useful unless there are other IPFSCluster resources on other Kubernetes clusters which are able to reach them. Therefore, we want to be pulling in a secret via key reference and an IP4/IP6 address of the original IPFS Cluster peer
The text was updated successfully, but these errors were encountered: