How to deploy K3S cluster on RancherOS nodes connected via a Zerotier network.
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
# Run with Python 3 | |
import json | |
import requests | |
# 1. Get your keys at https://stepic.org/oauth2/applications/ (client type = confidential, authorization grant type = client credentials) | |
client_id = ... | |
client_secret = ... | |
# 2. Get a token |
My attempt at gathering information on how to detect exactly which Raspberry Pi model we are running on for https://github.com/jperkin/node-rpio. The goal is to come up with an optimal way of detecting the host across a wide range of hardware and OS.
Name (Rev) | cpuinfo |
/proc/device-tree/model |
device-tree/soc/ranges |
OS |
---|---|---|---|---|
B (1.0) | 0002 |
Raspberry Pi Model B |
7e000000 20000000 01000000 |
7 |
B (1.0) | 0002 |
Raspberry Pi Model B Rev 1 |
7e000000 20000000 02000000 |
10 |
This guide will walk you through how to set up and use the proof of concept Rancher OS Management capabilities. It was written on March 23rd 2022. If you notice any errors, please reach out to me on the rancher-users.slack.com either through a DM to Andrew Gracey or the #cos-toolkit channel (cOS was the old name of Elemental)
Pre-reqs:
- Rancher Manager 2.6.x
- Docker or Rancher Desktop
- Server or VM with TPM 2.x
Notes:
- Until release of SLE Micro 5.2, we will be using an OpenSUSE base image