Skip to content

manuelbuil/rke2

This branch is 1 commit ahead of, 283 commits behind rancher/rke2:master.

Folders and files

NameName
Last commit message
Last commit date

Latest commit

4d093c5 · Apr 11, 2024
Apr 10, 2024
Feb 9, 2024
Apr 8, 2024
Aug 16, 2021
Apr 4, 2024
Apr 4, 2024
Apr 11, 2024
Apr 8, 2024
Apr 10, 2024
May 2, 2023
Aug 11, 2023
Oct 17, 2022
Sep 28, 2020
Mar 15, 2024
Sep 25, 2023
Apr 28, 2023
Jul 31, 2021
Sep 25, 2020
Aug 28, 2020
Apr 8, 2024
Jun 23, 2021
Mar 8, 2024
Apr 17, 2020
Jul 31, 2023
Apr 8, 2024
Jun 12, 2023
Oct 3, 2023
Mar 22, 2024
Apr 4, 2024
Apr 4, 2024
Nov 28, 2022
Jan 3, 2024
Feb 11, 2023
Dec 5, 2023
Oct 13, 2022

Repository files navigation

RKE2

RKE2

RKE2, also known as RKE Government, is Rancher's next-generation Kubernetes distribution.

It is a fully conformant Kubernetes distribution that focuses on security and compliance within the U.S. Federal Government sector.

To meet these goals, RKE2 does the following:

For more information and detailed installation and operation instructions, please visit our docs.

Quick Start

Here's the extremely quick start:

curl -sfL https://get.rke2.io | sh -
systemctl enable rke2-server.service
systemctl start rke2-server.service
# Wait a bit
export KUBECONFIG=/etc/rancher/rke2/rke2.yaml PATH=$PATH:/var/lib/rancher/rke2/bin
kubectl get nodes

For a bit more, check out our full quick start guide.

Installation

A full breakdown of installation methods and information can be found here.

Configuration File

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.

By default, RKE2 will launch with the values present in the YAML file located at /etc/rancher/rke2/config.yaml.

An example of a basic server config file is below:

# /etc/rancher/rke2/config.yaml
write-kubeconfig-mode: "0644"
tls-san:
  - "foo.local"
node-label:
  - "foo=bar"
  - "something=amazing"

In general, cli arguments map to their respective yaml key, with repeatable cli args being represented as yaml lists. So, 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 $RKE2_CONFIG_FILE.

FAQ

Security

Security issues in RKE2 can be reported by sending an email to security@rancher.com. Please do not open security issues here.

About

No description, website, or topics provided.

Resources

License

Stars

Watchers

Forks

Packages

No packages published

Languages

  • Go 65.5%
  • Shell 18.1%
  • PowerShell 11.3%
  • Ruby 1.3%
  • Python 1.2%
  • Dockerfile 1.0%
  • Other 1.6%