ipfs-operator
ipfs-operator copied to clipboard
ipfs-cluster
fixes: [https://github.com/ipfs-cluster/ipfs-operator/issues/95](https://github.com/ipfs-cluster/ipfs-operator/issues/95) fixes: [https://github.com/ipfs-cluster/ipfs-operator/issues/96](https://github.com/ipfs-cluster/ipfs-operator/issues/96) Below are the changes made in this PR - Inherited config type from ipfs-cluster - Added mechanism to build and modify service.json inside operator. - Added...
Only internally because usually Prometheus/Thanos are run inside the same Kubernetes cluster. So we need to just expose metrics from ipfs-cluster to other namespaces.
Currently service.json is created using the command [ipfs-cluster-service init](https://github.com/ipfs-cluster/ipfs-operator/blob/main/controllers/scripts/config.go#L89) which makes it difficult to customize ipfs-cluster via modifying service.json file. Here idea is to create service.json inside the operator code...
ETA: 2023Q2 Description: Identify new or existing gateway, cluster, or pinning service installations that can use the IPFS operator. We will engage with hackathons, or conferences to identify use cases...
ETA: 2023Q1 Description: Run the operator through its paces. This is important for several reasons. * gateways are a primary use case, and we want to understand expected performance characteristics...
ETA: 2023Q2 Description: this is an immediate application P.L. can use to dogfood the operator. In 2023, we will be hosting the filecoin snapshots on IPFS, and we should use...
ETA: 2023Q1 Description: Common IPFS problems are solved by using the operator. The IPFS operator is a turn-key solution for the following common applications: * running a gateway * IPFS...
fixes: https://github.com/ipfs-cluster/ipfs-operator/issues/72 fixes: https://github.com/ipfs-cluster/ipfs-operator/issues/71