Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Running in a Private Network #81

Open
RobotSail opened this issue Oct 17, 2022 · 0 comments
Open

Running in a Private Network #81

RobotSail opened this issue Oct 17, 2022 · 0 comments
Assignees

Comments

@RobotSail
Copy link
Collaborator

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

@RobotSail RobotSail self-assigned this Oct 17, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant