IPFS, NAT and k8s

jimpick · September 12, 2019, 2:14pm

You could set to set your “Announce” address to “/ip4/44.222.33.555/tcp/32639/ipfs/QmVyKLpva…” in the Addresses section of the IPFS config file.

github.com

ipfs/go-ipfs/blob/master/docs/config.md#addresses

# The go-ipfs config file

The go-ipfs config file is a JSON document located at `$IPFS_PATH/config`. It
is read once at node instantiation, either for an offline command, or when
starting the daemon. Commands that execute on a running daemon do not read the
config file at runtime.

#### Profiles

Configuration profiles allow to tweak configuration quickly. Profiles can be
applied with `--profile` flag to `ipfs init` or with the `ipfs config profile
apply` command. When a profile is applied a backup of the configuration file
will be created in `$IPFS_PATH`.

Available profiles:

- `server`

  Recommended for nodes with public IPv4 address (servers, VPSes, etc.),
  disables host and content discovery in local networks.

This file has been truncated. show original

Topic		Replies	Views
IPFS Peer ID getting set as localhost - K8s	6	816	February 27, 2020
IPFS node in kubernetes having no inbound peers Kubo go-ipfs	4	324	November 30, 2023
IPFS on Kubernetes Coding go-ipfs , kubernetes	5	2818	June 16, 2020
IPFS node, Minikube, Kubernetes IPFS go-ipfs , kubernetes	7	746	November 2, 2021
IPFS Node and vpn providers	7	2463	September 25, 2019

IPFS, NAT and k8s

Related topics