- 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
- Separate out the Manually Deploy Images method from the Private Registry method
-- Explain the caveat with manual image deployment (could be unmanagable for larger clusters)
- Show separate tabs for installing in a single server configuration or HA configuration
- Update the upgrade section to include the system upgrade controller
- Various tweaks throughout to improve readability
- Mentions that the flag is experimental (CLI help also indicates this)
- Explains what happens when the experimental flag is enabled
- Explains what happens if you disable the flag and try to read secrets
- Specifies the version that was certified with Amazon RDS
- Updates the Mysql tab in the "Datastore Endpoint Format and Functionality" section to include MariaDB
Historically, k3s binaries have grown from less than 40 MB in size in the original release to more than 40 MB today.
Therefore, the actual size should be corrected to avoid misunderstanding.
Catherine Luse
David Nuzik
Catherine Luse
Craig Jellick
David Nuzik
galal-hussein
Michael Foley
Stuart P. Bentley
Sam Kleiner
Nic de Sousa
Tetsurou YANO