A significant number of the different configuration options are described in their respective documents only in terms of command-line argument passed to the rke2 binary, significantly burying the lede on being able to configure the server using the same keys and values in config.yaml.
Given that the quickstart install directions lead you to a configuration where changing the server's command line arguments is rather not straightforward, I'd wager that the config.yaml method is probably far more useful to most people following those directions, and information on how to do this needs to be a lot more prominent than it currently is, buried between several other less-relevant sections.
If nothing else, the section describing the equivalence between command-line arguments and config.yaml keys should be made a lot more prominent and discoverable. But I'd even argue that the config.yaml syntax should probably be the primary way of describing the configuration options themselves, with the command-line syntax only secondary.
For instance, take this paragraph:
To enable Multus, pass multus as the first value to the --cni flag, followed by the name of the plugin you want to use alongside Multus (or none if you will provide your own default plugin). Note that multus must always be in the first position of the list. For example, to use Multus with canal as the default plugin you could specify --cni=multus,canal or --cni=multus --cni=canal.
IMO this would probably be more useful if paragraphs like that were rewritten something along the lines of:
To enable Multus, add multus as the first list entry in the cni config key, followed by the name of the plugin you want to use alongside Multus (or none if you will provide your own default plugin). Note that multus must always be in the first position of the list. For example, to use Multus with canal as the default plugin you could specify:
# /etc/rancher/rke2/config.yaml
---
cni:
- multus
- canal
This can also be specified with command-line arguments, i.e. --cni=multus,canal or --cni=multus --cni=canal.
That paragraph above is actually specifically the one I just spent two days stumped on before finally figuring it out.
Just to describe my own experience here:
I had RKE2 set up and installed from the quickstart guide. I knew that I needed Multus for my use-case, and was able to find the Using Multus section, and therefore "knew" that I somehow needed to get --cni=multus,canal passed as a command-line argument... and then spent the next two days going down dead ends, reinstalling RKE2 half a dozen times, even just reading the RKE2 source code (e.g. to see if there was some undocumented option that would get the https://get.rke2.io installer script to append --cni=multus,canal to the ExecStart line in the rke2-server.service systemd unit file it created). It wasn't until near the end of day 2 combing through the docs and reading every bit on every page that I finally found what I needed with the config.yaml file.
![dependabot[bot] avatar](https://avatars.githubusercontent.com/in/29110?v=4 "dependabot[bot]")
![github-actions[bot] avatar](https://avatars.githubusercontent.com/in/15368?v=4 "github-actions[bot]")
React
Typescript
Django
Laravel
Facebook
Microsoft
Google
Alibaba
D3
Tencent
