- Explains need for node-name to be set when hostname is null or localhost
- Explains the reasoning for this
- This commit squashes several created in the PR
- Addresses Craig's comment outlined here https://github.com/rancher/docs/pull/2488/files#r420489320
- This tweaks the /upgrades/basic and /upgrades/automate pages. The basic page now goes into more depth about the release channels -- outlining specific examples. The automated page now calls out a link directly to this section on the /basic page instead of linking to the channelserver github project.
- I called out in the "v1.18" example that this selects the LATEST in the specific minor release. This does not select stable (I don't want people to confuse that with a stable channel).
- Minor spelling fix
- Resolves symlink issue in single-server section of https://github.com/rancher/k3s/issues/1031
- The INSTALL_K3S_SYMLINK env var now has a description that explains what binaries symlinks are created for
- Addresses comment around node-requirements page (now installation-requirements) in issue https://github.com/rancher/k3s/issues/1031
- Accompslishes this by adding a table to list ports, we actually took from /rancher/v2.x/en/installation/requirements/ports networking section so both guides are in alignment
- Add alias to old node-requirements page on installation-requirements page so any old links / search engines will redirect node-requirements link accordingly
- Fix broken legacy iptables link for raspian at /k3s/latest/en/installation/installation-requirements/#operating-systems
- Fix broken installation requirements link at /k3s/latest/en/installation/ha/#2-launch-server-nodes
- Fix broken installation requirements link at /k3s/latest/en/networking/#open-ports
Addresses concerns outlined here: https://github.com/rancher/docs/pull/2381#pullrequestreview-382323414
- fix S.U.C. capitalization and format
- Remove S.U.C. explanation as this is coverd in the Automated Upgrades guide
- Rephrase and reformat things as recommended by Craig. the latest version of the S.U.C. manifest YAML is now hyperlinked and an example provided for v0.4.0