upstream/k3s
1
0
Fork 0
mirror of https://github.com/k3s-io/k3s.git synced 2026-04-07 02:15:03 -04:00
Code Issues Projects Releases Packages Wiki Activity Actions 4
k3s/docs/release/expanded/channel_server.md
Ben ade82387f7
Inclusive naming proposal (issue: #12110, Orlin Vasiliev) (#12383) 
* Inclusive naming proposal (issue: #12110, Orlin Vasiliev)

Basic renaming from 'master' to 'main' as primary branch according to https://github.com/cncf/foundation/blob/main/code-of-conduct.md#our-standards

Signed-off-by: Andrea Benini <andreabenini@gmail.com>
Signed-off-by: Derek Nola <derek.nola@suse.com>

* Additional replacement of master with main in E2E testing, Github Action workflows

Signed-off-by: Derek Nola <derek.nola@suse.com>

---------

Signed-off-by: Andrea Benini <andreabenini@gmail.com>
Signed-off-by: Derek Nola <derek.nola@suse.com>
Co-authored-by: Derek Nola <derek.nola@suse.com>
2025-09-24 08:52:28 -07:00

636 B
Raw Permalink Blame History

Update Channel Server

Once the release is verified, the channel server config needs to be updated to reflect the new version for “stable”.  

  1. Channel.yaml can be found at the root of the K3s repo.
    1. When updating the channel server a single-line change will need to be performed.  
    2. Release Captains responsible for this change will need to update the following stanza to reflect the new stable version of kubernetes relative to the release in progress.  
    3. Example: 
      channels:
  name: stable
  latest: v1.22.12+k3s1