This page focuses on the configuration options available when setting up RKE2:
- Configuring the installation script
- Configuring RKE2 server nodes
- Configuring RKE2 agent nodes
- Using the configuration file
- Configuring when running the binary directly
The primary way to configure RKE2 is through its config file. Command line arguments and environment variables are also available, but RKE2 is installed as a systemd service and thus these are not as easy to leverage.
Configuring the Installation Script¶
As mentioned in the Quick-Start Guide, you can use the installation script available at https://get.rke2.io to install RKE2 as a service.
The simplest form of this command is as follows:
curl -sfL https://get.rke2.io | sh -
When using this method to install RKE2, the following environment variables can be used to configure the installation:
||Version of RKE2 to download from GitHub. Will attempt to download the latest release from the
||Type of systemd service to create, can be either "server" or "agent" Default is "server".|
||Channel URL for fetching RKE2 download URL. Defaults to https://update.rke2.io/v1-release/channels.|
||Channel to use for fetching RKE2 download URL. Defaults to
||Method of installation to use. Default is on RPM-based systems
This installation script is straight-forward and will do the following:
- Obtain the desired version to install based on the above parameters. If no parameters are supplied, the latest official release will be used.
- Determine and execute the installation method. There are two methods: rpm and tar. If the
INSTALL_RKE2_METHODvariable is set, that will be respected, Otherwise,
rpmwill be used on operating systems that use this package management system. On all other systems, tar will be used. In the case of the tar method, the script will simply unpack the tar archive associated with the desired release. In the case of rpm, a yum repository will be set up and the rpm will be installed using yum.
Configuring RKE2 Server Nodes¶
For details on configuring the RKE2 server, refer to the server configuration reference.
Configuring RKE2 Agent Nodes¶
For details on configuring the RKE2 agent, refer to the agent configuration reference.
By default, RKE2 will launch with the values present in the YAML file located at
An example of a basic
server config file is below:
write-kubeconfig-mode: "0644" tls-san: - "foo.local" node-label: - "foo=bar" - "something=amazing"
The configuration file parameters map directly to CLI arguments, with repeatable CLI arguments being represented as YAML lists.
An identical configuration using solely CLI arguments is shown below to demonstrate this:
rke2 server \ --write-kubeconfig-mode "0644" \ --tls-san "foo.local" \ --node-label "foo=bar" \ --node-label "something=amazing"
It is also possible to use both a configuration file and CLI arguments. In these situations, values will be loaded from both sources, but CLI arguments will take precedence. For repeatable arguments such as
--node-label, the CLI arguments will overwrite all values in the list.
Finally, the location of the config file can be changed either through the cli argument
--config FILE, -c FILE, or the environment variable
Configuring when Running the Binary Directly¶
As stated, the installation script is primarily concerned with configuring RKE2 to run as a service. If you choose to not use the script, you can run RKE2 simply by downloading the binary from our release page, placing it on your path, and executing it. The RKE2 binary supports the following commands:
||Run the RKE2 management server, which will also launch the Kubernetes control plane components such as the API server, controller-manager, and scheduler.|
||Run the RKE2 node agent. This will cause RKE2 to run as a worker node, launching the Kubernetes node services
||Shows a list of commands or help for one command|
rke2 server and
rke2 agent commands have additional configuration options that can be viewed with
rke2 server --help or
rke2 agent --help.