๐Ÿ“ฆ wagoodman / pi-cluster-utils

โ˜… 1 stars โ‘‚ 0 forks ๐Ÿ‘ 1 watching
๐Ÿ“ฅ Clone https://github.com/wagoodman/pi-cluster-utils.git
HTTPS git clone https://github.com/wagoodman/pi-cluster-utils.git
SSH git clone git@github.com:wagoodman/pi-cluster-utils.git
CLI gh repo clone wagoodman/pi-cluster-utils
Alex Goodman Alex Goodman allow anyone to update screen d6a4922 6 years ago ๐Ÿ“ History
๐Ÿ“‚ master View all commits โ†’
๐Ÿ“ clients
๐Ÿ“ inky-service
๐Ÿ“„ .gitignore
๐Ÿ“„ install.sh
๐Ÿ“„ README.md
๐Ÿ“„ requirements.txt
๐Ÿ“„ README.md

Pi K8s Cluster Utilities

Requirements:

  • some pi's with K8s installed and running
  • an InkyPhat display attached to a single pi (where these utils run)
This repo provides two services:
  • inky.service: a RPC server that accepts requests from other services/nodes to update the InkyPhat screen with content.
  • k8s-status.service: a client to inky that monitors the status of K8s nodes and reports to the inky.service the status.
Why split these services up? Can't they be combined? Yes they can, however, I have other applications that are using the inky.service remotely to show auxillary information, so this architecture is useful for that purpose.