	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

	Hyperledger is committed to creating a safe and welcoming community for all. For more information please visit the Hyperledger Code of Conduct.

Attendance

Indy Node Controller

Controller purpose
- Network Restart
  - No Ledger Transaction
  - Nodes communicate "Action"
- Node Upgrades
  - Ledger Transaction
Current State
- Controller In seperate Container
- Mounting Docker Socket
- https://github.com/hyperledger/indy-node-container/tree/main/controller
The principal Controller solution mounting the host docker socket into the controller container might be re-discussed as well
- Controller Container mounting docker socket
  - We deliver the orchestrated setup
  - Problem: Indy Node calls apt to check for package upgrades before forwarding the upgrade to the controller!
- Process on Container Host
  - Quick and Dirty
    - Needs Docker rights
      - Security Implications!
  - Greatest flexibility
  - Needs to survive restarts → e.g. systemd
  - Not worth it
- Kubernetes Operator
  - Needs Kubernetes Setup
    - Local install (e.g. K3S) not to dificult
    - But high maintenance effort
    - For production: Tell people to go to a Kubernetes provider!
  - Advantage: Runs on e.g. open shift, google, amazon, etc.
  - Clean Setup with pure container tech
  - Currently: probably to much effort for nobody in ID Union using a Kubernetes based setup
  - Biggest problem: No ressources in our group to develop this

We keep the current setup of running the Controller.
We Issue a Change proposal in indy node to refactor all upgrading into the controller