bluetooth-operator

bluetooth-operator lets you pair a Bluetooth game controller or remote with kubectl, and then give it to exactly one pod on a liken cluster. The pod claims the controller by its MAC address and gets that controller’s input devices, and no other input device on the machine.

What you can do:

• Pair a DualSense from your desk. Create a PairingRequest, put the controller in pairing mode, and approve the address that the radio reports. Pairing is an API, so RBAC controls who can pair, and nobody needs a shell on a node or in a pod.
• Give the controller to one pod. A game or emulator pod claims the controller by its address and gets its /dev/input/event* nodes. No other pod gets that input, and the pod gets no other input device.
• Wait for a controller that’s switched off. A paired controller stays published while it’s off. A pod that claims it stays Unschedulable, and starts when somebody turns the controller on.
• Keep the pairing across restarts. The pairing keys are in Secrets, so the controller can reconnect after a pod restart, an upgrade, or a reboot.

Start here:

• Install the operator .
• Pair a controller and give it to a pod .
• Devices : the devices, their attributes, and the claims that select them.

How it works

liken publishes the machine’s Bluetooth radio as a device. The operator’s pod claims the radio and runs bluetoothd itself, so the liken system image has no BlueZ and no D-Bus. The operator publishes each paired controller as its own device under the Dynamic Resource Allocation (DRA) driver bluetooth.liken.sh.

It also publishes the radio’s media bus, which audio-operator claims to play sound to paired Bluetooth speakers.

bluetooth-operator is one of the extension operators for claiming hardware . You install it only if your cluster needs Bluetooth.

• The source
• The liken manual