public/rancher-docs
1
0
Fork 0
mirror of https://github.com/rancher/rancher-docs.git synced 2026-09-28 05:59:03 +00:00
Code Issues Packages Projects Releases Wiki Activity

Modify About Channel Server section > Release Channels

Browse Source 
- 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
This commit is contained in:
David Nuzik
2020-07-27 16:18:06 -07:00
committed by Catherine Luse
parent 0221ded64b
commit 22aa4b50ea
2 changed files with 12 additions and 4 deletions
Download Patch File Download Diff File Expand all files Collapse all files
content/k3s/latest/en/upgrades/basic/_index.md
+11 -3
View File
@@ -7,9 +7,17 @@ You can upgrade K3s by using the installation script, or by manually installing
>**Note:** When upgrading, upgrade server nodes first one at a time, then any worker nodes.
### About the Channel Server
### Release Channels
The [channel server](https://github.com/rancher/channelserver) allows the install script to install or upgrade K3s within specific channels such as `stable` (default), `latest`, or `testing`. For additional channels, see [https://update.k3s.io/v1-release/channels](https://update.k3s.io/v1-release/channels).
Upgrades performed via the installation script or using our [automated upgrades]({{< baseurl >}}/k3s/latest/en/upgrades/automated/) feature can be tied to different release channels. The following channels are available:
| Channel | Description |
|---------------|---------|
| stable | (Default) Stable is recommended for production environments. These releases have been through a period of community hardening. |
| latest | Latest is recommended for trying out the latest features. These releases have not yet been through a period of community hardening. |
| v1.18 (example) | There is a release channel tied to each supported Kubernetes minor version. At the time of this writing, they are `v1.18`, `v1.17`, and `v1.16`. These channels will select the latest patch available, not necessarily a stable release. |
For an exhaustive and up-to-date list of channels, you can visit the [k3s channel service API](https://update.k3s.io/v1-release/channels). For more technical details on how channels work, you see the [channelserver project](https://github.com/rancher/channelserver).
### Upgrade K3s Using the Installation Script
@@ -63,7 +71,7 @@ To restart servers manually:
sudo service k3s restart
```
To restart agents mantually:
To restart agents manually:
```sh
sudo service k3s-agent restart
```