Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Update configuration.md #144

Merged
merged 2 commits into from
Jan 26, 2024
Merged

Update configuration.md #144

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
469187c
Update configuration.md
suryatejaboorlu Jan 6, 2024
15aa0c8
Update docs/install/configuration.md
suryatejaboorlu Jan 19, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/install/configuration.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -9,7 +9,7 @@ The primary way to configure RKE2 is through its config file. Command line argum
By default, RKE2 will launch with the values present in the YAML file located at `/etc/rancher/rke2/config.yaml`.

:::note
The RKE2 config file needs to be created manually. You can do that by running `touch /etc/rancher/rke2/config.yaml` as a privileged user.
The RKE2 config file needs to be created manually. You can do that by running `touch /etc/rancher/rke2/config.yaml` as a privileged user. If the configuration is changed after starting RKE2, the service must be restarted to apply the new configuration.
:::

An example of a basic `server` config file is below:
Expand Down