- Add an older-installations page, a child of the Installation main section to address older k3s versions different method for bringing up servers
- Modify the main HA install page so that we no longer list anything as experimental
-- Also update the page so we remove the Cluster Datastore Options section, compact this into a modified section of step 2 for bring up the master (server) nodes
-- Fix any wording, modify text so it's more readable and easier to follow.
- This changes the quick-start guide so we just remove the K3S_CLUSTER_SECRET environemnt variable. It wasn't needed for a simple quick-start.
- I changed the ha install guide so that we mention the K3S_CLUSTER_SECRET / --cluster-secret in this area as it would be likely relevant here i.e. for auto-scaling node pools.
- This makes changes to the quick-start and install guides that change wording around HA.
- Prevoiusly we only suggested HA for ALL production enviornments this is no longer the case. Single-server is okay if some down time is tolerable.
- This commit includes a couple of misc tweaks to fix wording in related areas.
* Move airgap from advanced to install
- move Air-Gap section in Advanced Options to Install Options
-- small tweak to the air-gap content but looks like may need more tweaks later
- update Installation Options _index.md so that it now lists "Air-Gap Installation" as an option with hyperlink
* Move airgap part 2 (actually del airgap from advanced)
Whoopsie. I forgot to remove the Air-Gap section from advanced in my last commit.
This simply deletes the Air-Gap section that used to be in the advanced page since we have moved the content to the installation/airgap section.
* Move ha backend options from configuration to install
- move storage backend options from the Configuration Info page to the Install Options (HA) page
-- small tweaks to content, very minor
* Move Uninstallation notes from advanced to install
- move note about Uninstallation from the Advanced Options page to Install Options main page
-- small tweaks to fix content and wording, very minor
* Fix and move upgrades content to main Install Options section
- In a previous commit, "Upgrades" section under the advanced section was mistakenly moved to the new airgap page
This fixes that and moves this content to the main install options section.
-- Some content tweaks to make the wording better and fix things up.
* Move networking info from Configuration Info to new Networking section
- Move networking info from confiuration to networking (new section)
* Move networking port info from configuration to networking
- Move some networking/security port info from the configuration page to the new networking page.
Note: This info is also intentionally already duplicated on the Node Registration page as it has important info on ports that need to be open and accessible.
* REMOVE "Building from Source" section completely
- Remove the Building from Source section
- Add FAQ Q&A about this and link to the k3s README.md where this info will go
Note: This was done after some discussion a while back. The Building from Source section is important, but not for the majority of users as release binaries / curl script should be utilized to install k3s.
A separate PR will add this content into the main k3s README.md file which the FAQ question that was added references.
* Fixes for comments, tweak ha install heading names
- Resolves comments asking to change headings in 2 areas of ha install
- Removes ambiguity in these areas
This tweaks the page weights so they make more sense.
We now have these in multiples of ten so we can easily move up or down new sections as we go beetween these numbers.
The Volumes and Storage section as added, intial only.
A separate commit will have the content for the Volumes and Storage page.
This adds an image representing a recommended configuration for HA k3s
This includes some context around the image
Later, we will tweak the HA page again before release to make some tweaks in a separate PR.
Update the main page for #1017 and #1018
This tweaks the main page to update the description of what we remove and add to k3s that sets us apart from k8s.
* Reorganize node requirements
* Cherry pick 'Fix links' commit
* Cherry pick 'Link to RKE port requirements for each node in Rancher docs'
* Fix merge conflict errors
* Delete page that was moved elsewhere
* Delete section that was included elsewhere
* Re-add port requirements for custom nodes
* Rearrange pages
* Change wording of note in Rancher installation requirements
* Fix links
* Edit links
* Edit links
* Replace user cluster requirements page
* Fix typo
* Fix link to imported cluster requirements
* Revise node requirements
* Add mini TOC for port requirements
* Remove alias for port requirements page