Peer resource, you can deploy ipfs peers which will join the public ipfs swarm by default.
Deploying this manifest will deploy a basic (but powerful 💪) ipfs peer which will starts with the all default settings that's similar to running
ipfs init then
ipfs daemon on your machine.
Let's deloy the above manifest.
Peer controller will get a notification that a new
Peer resource has been deployed, and will create all the Kubernetes resources (pod, service, configmap) necessary for it to work as expected. You can verify peer resources has been created by fetching all peers:
From the output above, we can confirm that ipfs peer
peer-sample has been deployed and using go-ipfs client.
Get the pod created by our peer:
Check the logs of the running peer:
You'll get output similar to the following:
Congratulations 🔥 your peer is up and running and ready to receive api calls.
Let's forward localhost:5001 calls to peer-sample container:5001
Let's read ipfs readme file by send http api call using cURL:
You'll get the following result:
You can view ipfs webui by visiting http://0.0.0.0:5001/webui
Finally, delete the ipfs peer
peer-sample, and Kubernetes will delete all resources created for the peer by kotal ipfs peer controller like pods, services ... etc: