ipfs-cluster/ipfs-operator

Issues

• IPFS operator Roadmap H1 2023

  #89 opened 2 years ago by coryschwartz
  0

• Is this alive?

  #101 opened 10 months ago by kenmoini
  1

• Create Images for ARM

  #86 opened 2 years ago by RobotSail
  0

• Road to initial release

  #75 opened 2 years ago by coryschwartz
  0

• Unused fields

  #82 opened 2 years ago by RobotSail
  0

• Add option to enable and expose Prometheus metrics internally to other pods

  #96 opened 2 years ago by patilsuraj767
  0

• Create service.json inside operator

  #95 opened 2 years ago by patilsuraj767
  0

• Community development

  #93 opened 2 years ago by coryschwartz
  0

• benchmark the gateway

  #92 opened 2 years ago by coryschwartz
  0

• use IPFS-operator to host filecoin snapshots

  #91 opened 2 years ago by coryschwartz
  0

• IPFS-operator is turnkey for common IPFS appications.

  #90 opened 2 years ago by coryschwartz
  0

• Update README.md

  #85 opened 2 years ago by RobotSail
  0

• Cannot create `config.json` when running in OpenShift

  #84 opened 2 years ago by RobotSail
  1

• Persistent storage for the cluster?

  #80 opened 2 years ago by leseb
  2

• publish to operatorhub

  #64 opened 2 years ago by coryschwartz
  0

• Running in a Private Network

  #81 opened 2 years ago by RobotSail
  0

• Optimize IPFS pod startup times

  #59 opened 2 years ago by RobotSail
  1

• Add end-to-end tests for IPFS Cluster

  #40 opened 2 years ago by RobotSail
  0

• bug: peerid mismatch

  #78 opened 2 years ago by coryschwartz
  1

• Rename CR to IPFSCluster

  #15 opened 2 years ago by RobotSail
  0

• Allow the reconciliation step to update configurations

  #66 opened 2 years ago by hsanjuan
  0

• include an optional gateway service

  #8 opened 2 years ago by coryschwartz
  1

• Improvements, problems and other suggestions

  #30 opened 2 years ago by hsanjuan
  2

• Read the Docs

  #41 opened 2 years ago by RobotSail
  2

• epic: documentation

  #63 opened 2 years ago by coryschwartz
  0

• Add reference to IPFS docs site

  #62 opened 2 years ago by coryschwartz
  1

• Reference IPFS Operator on IPFS cluster website

  #61 opened 2 years ago by coryschwartz
  1

• Implement a sidecar to manage connectivity and configuration changes in the cluster

  #48 opened 2 years ago by hsanjuan
  0

• IPFS daemons are peered to the relays using the relay's external IPs and not their internal ones (probably it does make a difference)? AddrFilters configuration needs to be adjusted for this to work.

  #34 opened 2 years ago by RobotSail
  2

• Add option to expose IPFS gateway externally

  #72 opened 2 years ago by coryschwartz
  0

• Add option to expose the API externally.

  #71 opened 2 years ago by coryschwartz
  0

• It would be good to allow to configure the reprovider strategy.

  #37 opened 2 years ago by RobotSail
  0

• The bloomfilter size should be adjusted automatically

  #35 opened 2 years ago by RobotSail
  1

• unit testing

  #22 opened 2 years ago by RobotSail
  0

• ipfs configuration has no bootstrappers

  #65 opened 2 years ago by hsanjuan
  0

• expose pinning port internally

  #9 opened 2 years ago by coryschwartz
  1

• newly created cluster members should join the existing cluster

  #7 opened 2 years ago by coryschwartz
  1

• Implement cluster following

  #10 opened 2 years ago by coryschwartz
  1

• Prevent helm image templates from being overridden

  #58 opened 2 years ago by RobotSail
  0

• Accelerated DHT client should be enabled in the configuration

  #36 opened 2 years ago by RobotSail
  1

• EnableHolePunching -> false.

  #38 opened 2 years ago by RobotSail
  1

• We should disable quic endpoints in the swarm section and settle on tcp only.

  #39 opened 2 years ago by RobotSail
  1

• We should be using flatfs/next-to-last/3 (which means we need to initialize config from a template). Currently using badger.

  #32 opened 2 years ago by RobotSail
  5

• IPFS daemons are currently not announcing their kubernetes internal IP (per the NoAnnounce and the AddrFilters) configuration. This means they likely won't connect directly to each others. Ideally they shoud be allowed to scan their LAN.

  #33 opened 2 years ago by RobotSail
  4

• Add golangci-lint as action

  #27 opened 2 years ago by RobotSail
  0

• Skip image rebuild in CI

  #45 opened 2 years ago by RobotSail
  0

• Add bootstrap scripts for kind

  #14 opened 2 years ago by RobotSail
  1

• KIND Install Script

  #17 opened 2 years ago by RobotSail
  1

• bug: containers might crash in a way that they can't start again

  #29 opened 2 years ago by coryschwartz
  0

• Add Helm Charts

  #16 opened 2 years ago by RobotSail
  1