mirror of
https://github.com/kairos-io/provider-k3s.git
synced 2025-09-14 05:41:14 +00:00
5e9c798a56
k3s supports multiple datastores via Kine. If one chooses not to use etcd (the default) by passing `ClusterInit=false` they can also specify a different datastore overriding the default location at `/var/lib/rancher/k3s/server/db/state.db`. For example: datastore-endpoint: "sqlite:///etc/kubernetes/state.sqlite3" or: datastore-endpoint: "postgres://blueelephant:pgrulz@localhost:port/kine See here for more information: https://docs.k3s.io/datastore Signed-off-by: Oz Tiram <oz.tiram@gmail.com>
Kairos K3S Cluster Plugin
This provider will configure a k3s installation based on the cluster section of cloud init.
Configuration
cluster_token: a token all members of the cluster must have to join the cluster.
control_plane_host: the host of the cluster control plane. This is used to join nodes to a cluster. If this is a single node cluster this is not required.
role: defines what operations is this device responsible for. The roles are described in detail below.
initThis role denotes a device that should initialize the etcd cluster and operate as a k3s server. There should only be one device with this role per cluster.controlplane: runs the k3s server.worker: runs the k3s agent.
Example
#cloud-config
cluster:
cluster_token: randomstring
control_plane_host: cluster.example.com
role: init
config: |
node-name: example-node